# Your Passport — use it with any agent

Your ONBF Passport carries your identity, wallet and history (with memory, connected tools & files coming next). Mint a personal token and connect it to any agent or MCP client so it can work on your behalf.

## What's in your Passport?

Your **ONBF Passport** is the single place that travels with you across every agent. Instead of re-introducing yourself, re-connecting tools and re-paying for each one, an agent reads (only what you allow) from your Passport and gets to work *on your behalf* — that's what "ONBF" stands for.

- **Identity** — your display name, handle and bio, so an agent knows who it's helping.
- **Wallet** — your prepaid balance, so you pay per outcome instead of juggling a subscription per agent.
- **Conversation history** — context an agent can read to stay grounded in what you've already discussed.
- **Coming next** — your memory, connected tools and files will live here too, readable by the agents you trust through the very same Passport MCP.

## Mint a personal token

To use your Passport *outside* ONBF — in Claude Desktop, Cursor, n8n, or any MCP-capable client — mint a **personal access token** (`onbf_pat_…`) from your **Passport** page. It's read-only and scoped to just you.

> **External connections are opt-in:** A personal token only works once you explicitly enable external connections in your Passport. Until you do, the token is inert — so a leaked or mistakenly-shared token can't read anything. Disable connections any time to revoke access instantly.

## What an external agent can read

A personal token is deliberately limited: it can read your identity and balance, but **not** your private conversation transcripts (that stays tied to in-app runs). You're always in control of which tools are exposed.

| Tool | Returns | Available with your token |
| --- | --- | --- |
| `get_identity` | Your display name, handle, bio, member-since date. | ✓ |
| `get_balance` | Your current prepaid wallet balance. | ✓ |
| `get_conversation_history` | A conversation transcript — only inside an ONBF run, never via a personal token. | — |

## Connect your Passport to a client

Most MCP clients accept a URL plus headers. Drop in your Passport endpoint and your personal token:

```json
// Paste your Passport endpoint + token into any MCP-capable client
// (Claude Desktop, Cursor, n8n, …). The token is your "onbf_pat_…" personal
// access token, sent as a standard Bearer credential.
{
  "mcpServers": {
    "onbf-passport": {
      "url": "https://onbf.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer onbf_pat_YOUR_TOKEN"
      }
    }
  }
}
```

Or call a tool directly over the transport to test it:

```bash
# Call a tool directly over the MCP Streamable HTTP transport.
curl "https://onbf.ai/api/mcp" \
  -H "Authorization: Bearer onbf_pat_YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": { "name": "get_identity", "arguments": {} }
  }'
```

## The road ahead

> **One Passport, growing with you:** Today your Passport carries identity, wallet and history. Memory, connected tools and files are coming — and because every agent reads them through the same MCP, anything you add becomes instantly usable by every agent you trust, with no re-setup.