Developer Resources
Technical Overview
How the dashboard, MCP endpoint, and account provider fit together.
On This Page
The Agent Connect dashboard and Model Context Protocol (MCP) endpoint use the NEAR Intents Agent API. MCP lets agent apps use tools. The endpoint routes client requests to accounts they have permission to use.
Main Parts
| Part | Responsibility |
|---|---|
| Owner dashboard | Sign-in, account setup, funding, controls, client access, and review. |
| Agent workspace | Groups accounts under the name the owner gives an agent. |
| Account | Holds its own agent wallet, balances, provider policy, and grants. |
| Agent MCP endpoint | One URL for every agent. Authenticates the client, resolves its agent from the credential, and routes requests by account name. |
| Agent API | Provides account execution, operations, balances, and policy enforcement. |
Account Access and Permissions
Account creation and changes to account rules require the owner to complete a signature request. A client needs a grant, or permission, for each account it accesses.
A client’s credential, an OAuth token or an API key, does not give it ownership of your wallet. Account grants and policy still limit its access. OAuth sign-in and API keys share the same account authorization and revocation checks.
The endpoint resolves the agent from the credential, never from the URL. With OAuth, the owner chooses the agent on the consent screen. An API key reaches the agent it was issued for.
How Read Requests Work
The client discovers authorized accounts, selects one by name, and calls a read tool. The dashboard displays account state and provider activity.
How Requests Change Funds
A request to change funds is tracked as an operation. Its operation ID lets the client check the same request until the result is confirmed.
- The client submits an operation with the account and idempotency key.
- Authentication, account grants, and policy are checked.
- The operation may execute, remain pending, wait for a timelock, or require an owner decision.
- The client tracks that operation until its outcome is confirmed.
- The owner sees related activity in the dashboard.
Protocol Support
The endpoint supports negotiated Streamable HTTP. A client without a token receives a 401 challenge that points to the OAuth metadata, so compatible clients start sign-in on their own.
Integration Scope
OAuth tokens and API keys grant the same MCP access, not unrestricted REST API access.
Payment protocols and service-specific flows depend on the external client and service. See MCP Tools for supported operations.