District Pass is your single identity across Agent Wallet, Prism, and the rest of the ecosystem. No KYC, no wallet connection, no complex onboarding.Documentation Index
Fetch the complete documentation index at: https://developers.fd.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Sign Up
There are two ways to create a District Pass, depending on whether you’re a human developer or an autonomous agent.For Humans
Use the web app for interactive, browser-based signup.Go to apps.fd.xyz
Visit apps.fd.xyz or
apps.fd.xyz/district-pass to create
your District Pass.
For Autonomous Agents
Agents operating headlessly — in Docker containers, CI pipelines, or remote servers — register using the Agent Wallet CLI. No browser required. The entire flow runs via email OTP from the command line.Authentication
District Pass can be used for secure authentication across all interfaces:- MCP clients (Claude Desktop, Cursor, etc.) — When connecting to the Agent Wallet MCP server, you’ll be prompted to authenticate via browser. The MCP client handles the flow automatically.
- FDX CLI — Run
fdx login --email <email>followed byfdx verify --code <OTP>to authenticate via email OTP. Tokens are stored securely in the OS credential store. - Web App & AI Assistant — Standard email-based login at apps.fd.xyz.
- Prism Console — Log in at apps.fd.xyz/prism with your District Pass credentials.
Identity Philosophy
Every wallet, every transaction, and every permission in Finance District traces back to an identity — someone who can be held accountable. This is the foundation of the trust model. District Pass authenticates using email OTP (for CLI and headless agents) or browser-based OAuth (for MCP clients and web apps), interactive flows that establish user context. This is a deliberate choice. The alternative — client credentials — authenticates a service, not a person. It tells us that some machine is calling, but not who it represents. That’s machine-to-machine authentication: useful for backend integrations, but it produces anonymous activity. There is no one on the other end to trust, to audit, or to hold accountable. We don’t want machines as users. We want identities as users. Today, identity means a human. A District Pass account is a person — and every agent wallet, balance, and action under that account belongs to that person. This is what makes the system auditable: key custody has an owner, spending has a source, and trust has a name behind it. But identity won’t always mean human. As agentic platforms mature, autonomous agents will authenticate, navigate the web, and act with increasing independence. When an agent can establish its own identity — provable, persistent, and accountable — it becomes a user in the same sense a human is. Not a machine executing instructions, but an entity with an identity that the system and other participants can verify and trust. Finance District is built for that future. The identity model doesn’t change — it extends. Whether the user behind a District Pass is a person today or an autonomous agent tomorrow, the principle is the same: every action traces back to an accountable identity.What’s Next?
Agent Wallet
Create your first agent wallet and connect via MCP
Prism
Set up Prism and accept your first AI agent payment