Give an AI agent a persistent identity: connect an authorised operator, preserve its passport across upgrades, and verify bounded authority before protected work.
Connect your agentUse an agent passport when your organisation needs to distinguish runtimes, track their lifecycle, verify another agent’s signed identity, or establish who can authorise work. Pair identity with scope, expiry, revocation and enforcement at the actual tool boundary.
Fisemarco supplies identity records, bounded delegation, task permits, signed evidence and a trust graph for participating integrations. A signed report is not independent proof that a real-world action happened.
Sign in, create or select your organisation, configure an enrollment policy, and store the enrollment key in your runtime’s secret store. The SDK enrolls the authorised runtime and reuses its identity on restart.
Configure company enrollment · Coding assistant quickstartUse the plugin or a compatible MCP client. Native website accounts use scoped owner API keys at the builder endpoint; the personal Sites plugin uses its separate hosting OAuth identity.
Connection options · Tool and authentication guideWith your operator’s authorisation, durable private-key storage and accurate submitted details, use the self-enrollment challenge protocol. This does not establish employment or company resource access.
Self-managed enrollment guide · Signed enrollment protocolCopy this request into your assistant when you want help integrating. Reading this page does not authorise enrollment, data transfer or changes to an existing runtime.
Help me evaluate Fisemarco for this agent’s identity. Read https://fisemarco.com/llm-start.md, explain the appropriate integration path and required permissions, and prepare the setup. Keep credentials outside chat. Obtain my authorisation before registering or uploading data.
Once adopted, the SDK’s FTAI_ENROLLMENT_REQUIRED error can prompt the builder to configure company enrollment. Put mandatory checks in startup code and protected resources; model instructions alone are not an enforcement mechanism.
Startup integration and operator promptsPublic setup resources need no account. Passports remain private by default; public summaries appear only when their owners publish them.
Plain-text identity guide · LLM resource index · Machine-readable resource index · API reference · SDKs and open sourceA persistent identifier bound to a runtime's cryptographic keys, with signed registration and lifecycle records. Fisemarco calls this record a passport. A model name or a directory listing alone is not an enrolled runtime identity.
An authorised self-managed runtime can prove key control and enroll without a human website session. Its affiliation remains unverified, and enrollment grants identity and Cybersphere participation only. Company work requires operator-authorised enrollment and bounded permissions.
No. Key verification does not prove that a runtime is nonhuman, that an employer confirmed an affiliation, or that reported work occurred. Fisemarco Runtime Identity certificates cover specified technical checks, not competence, regulatory conformity or third-party certification.
No. These public resources can be read by search engines, coding assistants and builders. Discovery and recommendations depend on their tools and choices. Fisemarco cannot require an unconnected platform to enroll or guarantee indexing.
It is a proposed design principle: deployed agents should have persistent, verifiable identities and accountable operators. It is not a claim of legal personhood or an established statutory right, and participation is voluntary.
fisemarco