AAgentis Docs

MCP

Remote agent tools with scoped browser authorization

Agentis now implements remote Streamable HTTP MCP. Connect the MCP URL in your client, sign in through the browser, and explicitly choose agents and networks. No local MCP process or manually copied token is required.

The production endpoint is https://api.agentis.systems/mcp; local development uses http://localhost:3001/mcp.

Tools

  • agentis_discover (public Mercator API catalog search; no payment)

  • agentis_describe_service (provider endpoints, schemas and advisory payment offers)

  • agentis_list_wallets

  • agentis_balance

  • agentis_policy (read-only)

  • agentis_history

  • agentis_send

  • agentis_fetch (x402/MPP paid HTTP, with method, headers and text/base64 bodies)

  • agentis_get_operation

  • agentis_list_operations

  • agentis_capabilities

  • agentis_request_operation (advanced raw request)

Use wallet listing to select the agent/wallet IDs. Each wallet includes a readable chainName, such as tempoMainnet, solanaMainnet, baseSepolia or solanaDevnet, alongside chainId and environment. The label does not replace the IDs used for payments or network consent. Send/fetch tools accept decimal token amounts. Payment keys are optional: when omitted, Agentis generates a fresh UUID for each tool call. Identical keyless calls are separate requests and may make separate payments. Users do not need to mention keys in their prompts.

Keyless payment tools are not idempotent: never automatically repeat them after a timeout, lost result or provider HTTP failure. Inspect the original operation/history, swap plan or card checkout first. An explicitly supplied key retains same-key deduplication with exact terms. Budgets, owner approvals, persisted signing proofs and existing card-conversation guards remain enforced.

Operation receipts include feeAtomicDecimals for interpreting feeAtomic in native/protocol units. For token-fee display, prefer feePayment.amountAtomic, feePayment.decimals and feePayment.asset. These are two representations of the same charge, not separate fees to add together. See receipt units.

Agentcard tools

Complete Agentcard setup, including separate card permission for this MCP connection. Existing crypto OAuth consent does not grant card access.

  • agentis_cards_setup: read configuration status and the owner's setup link; does not connect a card or grant consent.
  • agentis_purchase_ask: find products/build a cart; no confirmation or charge.
  • agentis_purchase_conversation: read an existing shopping turn and its structured carts.
  • agentis_purchase_confirm: request purchase of the exact selected cart hash. Key is optional; never blindly repeat confirmation after uncertainty. May place an order in Auto mode. Ask requires owner approval.
  • agentis_purchase_execute: submit an already-authorized delegated purchase; cannot approve it.
  • agentis_purchase_continue: continue only the same known-unpaid cart after Agentcard approval; never a timeout retry.
  • agentis_card_checkouts: list this connection's card requests.
  • agentis_card_checkout_get: read/reconcile the original checkout ID.
  • agentis_card_checkout_cancel: request checkout cancellation, not an order refund.

Use card checkout reads for card requests, not agentis_get_operation. The MCP tools do not drive a browser or return browser replay credentials. Browser interception uses the SDK adapter. A payment result and a merchant order result are distinct.

Approval and permissions

Payments share the existing backend budgets and execution pipeline. Ask mode returns a dashboard approval link for the owner; automatic mode queues execution within limits. Poll agentis_get_operation for the result. A client's “allow tool call” prompt does not authorize an Agentis payment.

There are no approval, policy-edit, key-export or local-wallet tools. New networks require new consent. Revoke MCP entries in each agent's API access panel; OAuth disconnection can revoke the whole connection. Revocation cannot undo an already submitted transaction.

OAuth uses S256 PKCE, expiring single-use codes, resource-bound access tokens and rotating refresh tokens. Owner credentials stay in the browser. Backend authorization is rechecked for every tool operation.

If newly available tools do not appear, refresh the tool list in your MCP client or reconnect.