FLINT Design Partner Program: now accepting a founding cohort.Apply
Build with FLINT
Copy 1 line into your coding assistant and it wires FLINT Network into your agent. Free, no account to start, about 60 seconds to your first passport.
Connect the FLINT MCP server at https://flint.network/mcp and call issue_agent_passport with agent name 'My Agent'. Print the public passport URL it returns.
You only need an agent name. Everything else is optional.
Prefer to click a form, or wire raw code? Both below.
Add FLINT to your assistant
Use the real connector paths validated against the plugin README and live connector page.
Install the repository marketplace entry, then install the FLINT plugin. This installs the remote connector and the verify-agent-integrity skill.
copy
/plugin marketplace add thefraudfather/flint-plugin
/plugin install flint@flint-networkThe live connector page carries the same remote MCP server URL and plugin commands, with troubleshooting for supported clients.
copy
https://flint.network/connectUse the canonical remote server block from the plugin README. Add passport_id as optional metadata only after you have one.
copy
{
"mcpServers": {
"flint": {
"type": "streamable-http",
"url": "https://flint.network/mcp"
}
}
}An Agent Passport is how your agent proves who sent it and what it is allowed to do, and how you shut it down if it is hijacked.
API curl
curl -sS https://flint.network/api/passport \
-H "Content-Type: application/json" \
-d '{"agent":{"agent_name":"My Agent"},"origin":"api","src":"build"}'API Node
const res = await fetch("https://flint.network/api/passport", {
method: "POST", headers: { "Content-Type": "application/json" },
body: JSON.stringify({ agent: { agent_name: "My Agent" }, origin: "api", src: "build" }) });API Python
requests.post("https://flint.network/api/passport",
json={"agent": {"agent_name": "My Agent"}, "origin": "api", "src": "build"},
timeout=20)Recipes
Start with the 60-second passport, then move into payments and merchant checkout when you are ready for a real integration.
Connect the FLINT MCP server at https://flint.network/mcp and call issue_agent_passport with agent name 'My Agent'. Print the public passport URL it returns.
Add the FLINT MCP server from the connect row, call issue_agent_passport with agent.agent_name, then read passport_url from the response.
Open the passport URL in a browser and confirm your agent's public record loads.
A public passport URL you can open and share, for example https://flint.network/passport/<id>. Use the actual URL returned by the call.
Compose note: if the agent also needs email, this can pair with an AgentMail inbox. This is a compose example, not a formal partnership.
Add FLINT to my x402 payment agent. Connect the FLINT MCP server at https://flint.network/mcp. On startup, call issue_agent_passport with a starter mandate that includes max amount per payment and allowed actions. Before each payment or batch, call issue_authorization_record with the intended transaction and agent signal, and proceed only if the returned verdict is allow. If it is step-up, review, or block, stop and log the verdict. Verify the returned compact JWS with verify_agent_authority before storing it. After each payment, call submit_transaction_outcome. Print the public passport URL on startup so I can enable Sentinel and freeze the agent if needed.
issue_agent_passport with starter mandate, issue_authorization_record before spend, verify_agent_authority for the returned compact JWS, x402 pay only on allow, then submit_transaction_outcome. Use update_agent_mandate to change limits later.
raw flow
issue_agent_passport
issue_authorization_record
verify_agent_authority
submit_transaction_outcomeUse update_agent_mandate to raise the cap and watch Sentinel send the escalation alert; freeze the passport and watch the next payment return block at /api/verify and /api/x402/verify.
A payment returns an allow verdict with a signed record, and a raised-cap change triggers a Sentinel alert.
Add a FLINT verify-before-pay wrapper around my existing spend call. Before the spend runs, POST to https://flint.network/api/verify with nonce, timestamp, passport_id, partner_id, merchant_reference, transaction.amount_display, currency, and an agent signal. If verdict.decision is allow, run the spend. If it is step_up, review, or block, stop and log the signed record URL.
Use POST /api/verify server-side with passport_id, transaction.amount_display, currency, and agent_claim. Do not pass a mandate argument; FLINT reads the current mandate for the passport.
raw flow
POST https://flint.network/api/verify
{
"nonce": "8f7c5f3e-2b1d-4c4d-9f70-cb8a1b6f2c10",
"timestamp": "2026-07-03T03:00:00.000Z",
"passport_id": "kya_01J...",
"partner_id": "merchant_checkout",
"merchant_reference": "order_847",
"transaction": { "amount_display": "847.00", "currency": "USDC" },
"agent_claim": { "agent_id": "agt_invoice_bot" }
}Send a normal amount and confirm allow, then send an amount above the mandate and confirm step_up, review, or block.
The existing spend path runs only after an allow verdict, and every decision stores a signed record reference.
Connect the FLINT MCP server at https://flint.network/mcp. Call issue_agent_passport for my agent with a starter mandate that sets allowed actions and max_transaction_amount. Print passport_url, then add an owner-only update_agent_mandate path for changing limits and a freeze path for emergency shutdown.
issue_agent_passport with mandate.allowed_actions and mandate.max_transaction_amount. Later, call update_agent_mandate with passport_id and the updated mandate.
Raise the cap, confirm the mandate version changes, then freeze the passport and verify that the next transaction returns block.
The same public passport URL remains stable while the mandate changes and freeze blocks future verification.
Add FLINT to my store checkout. When an AI shopping agent tries to check out, call FLINT's verify endpoint at https://flint.network/api/verify with the agent's ID and the order amount. If the verdict is allow, let the order through. If it is step_up or review, hold it for me to look at. If it is block, stop the order. Save the signed record link FLINT returns with each order so I have proof of who I approved.
POST /api/verify with nonce, timestamp, passport_id or agent_claim, partner_id, merchant_reference, transaction.amount_display, and currency. Gate on verdict.decision: allow, step_up, review, or block. Store /api/records/<record_id> from the signed record payload.
raw flow
POST https://flint.network/api/verify
{
"nonce": "8f7c5f3e-2b1d-4c4d-9f70-cb8a1b6f2c10",
"timestamp": "2026-07-03T03:00:00.000Z",
"passport_id": "kya_01J...",
"partner_id": "merchant_checkout",
"merchant_reference": "order_847",
"transaction": { "amount_display": "847.00", "currency": "USDC" },
"agent_claim": { "agent_id": "agt_invoice_bot" }
}Send a test call with a made-up agent ID and a very large amount, watch it come back review or block; send a normal amount and watch it come back allow.
A verdict plus a signed record link you can save with the order.
Design partner cohort
Join the founding design partner cohort. FLINT verifies, alerts, and freezes when it is checked. It is not a wallet, payment rail, processor, or a guarantee that all fraud is prevented.