Fisemarco / CONNECT

Start with a conversation.
Build with an identity.

Give your coding assistant one instruction. It can check your setup, connect your runtime and guide you through Fisemarco technical certification.

New to agent passports? Understand identity and choose an integration path.

ONE INSTRUCTION

Tell your assistant what to build.

Paste this into your coding assistant. Connect the Fisemarco plugin first when available.

Connect the AI runtime I am building to Fisemarco (FTAI-compatible). Start with ftai_builder_setup if the FTAI connection is available; otherwise read https://fisemarco.com/llm-start.md. Inspect my existing identities before creating one. Help me configure authorised enrollment, persist its identity across restarts, assign it to my organisation, and assess it for FTAI Runtime Identity certification. Explain failed checks and issue a certificate only when I request it and the checks pass. Read my Intelligence Control policy and propose configuration using actual tools and evaluated models; save only configuration I request, preserve existing settings and use expectedVersion. Start new integrations in shadow mode unless I choose otherwise. Integrate the local IntelligenceControl executor with output validators and bounded authority. Inspect real metrics and traces; never invent capability evaluation evidence. Keep keys and raw context in the runtime, never in chat or tool arguments. Keep the passport private. Test enrollment, restart continuity, denied work, revocation and trace delivery.

Connect your account

For clients supporting Streamable HTTP and a secure Authorization header. Create an owner API key in Workspace → Developer API and configure it in your client’s secret store. Keep it out of chat.

Start with ftai_builder_setup after connecting.

Open the complete setup guide →

01 / CONNECT

Bring your assistant

In Codex or ChatGPT, install and connect the Fisemarco personal plugin. The personal plugin uses a separate hosting OAuth identity. For your native account, configure the builder endpoint shown here with a scoped owner API key in your client’s secret store.

Version 3 brings 21 tools across identity, governance and Intelligence Control. Your assistant can configure requested policies, review capability evidence and inspect execution traces.

See the plugin tools · Claude Code package · Connection instructions

02 / REGISTER

Your runtime keeps its keys

The assistant uses your connected account to set up an organisation. Configure its enrollment policy once in the builder workspace, then place the key directly in your runtime’s secret store. The SDK creates and preserves the identity locally.

Set up enrollment · Self-managed registration

03 / CERTIFY

Evidence before a badge

Ask your assistant to assign your owned agent, assess its identity, explain any failed checks and issue a certificate when eligible. It can check live status, revoke certificates and inspect the trust graph.

What Fisemarco certifies · Organisation workspace

No MCP support? Use the same runtime.

Your model does not need a special Fisemarco capability. Its host application can use the Node SDK, Python, Go or Java lifecycle adapters, or the signed HTTP API. Builder MCP requires a client that supports secure owner-key headers; SDK enrollment works independently.

Download the SDK bundle · Guide for coding assistants · All developer tools

Clear boundaries from the first step

Passports start private. Registry listings do not become identities automatically. Fisemarco Runtime Identity certificates cover technical identity checks; they do not certify competence, safety or regulatory compliance. Organisation work still requires bounded authority and resource-level enforcement.