A bounded swap path for AI agents
Parse an instruction, resolve canonical tokens, fetch a quote, build a bounded order, and submit it after local signing. Use MCP for the full tool path, the Intent API for parsing, or the SDK for direct control.
Last updated:
Choose the smallest integration surface
| Surface | Use it for | Auth |
|---|---|---|
| Hosted MCP server | Resolve, quote, build, validate, submit, and inspect chains | No API key |
| Intent API | Turn natural language into structured swap entities | No API key |
| @ophis/sdk | Build a custom chain-aware signing and orderbook flow | No Ophis key |
Connect an MCP-capable agent
Point a streamable-HTTP MCP client at https://mcp.ophis.fi/mcp. The server exposes
tools for token resolution, quotes, bounded-order construction, validation, submission, chain
discovery, balances, portfolios, gas, charts, and execution-quality estimates.
The safe sequence is explicit: resolve the canonical token, request a quote, build an order with the receiver pinned to the owner, validate the settlement domain, sign locally, then submit. The signature is the trust boundary.
Use the Intent API for natural-language parsing
Send POST https://ophis.fi/api/intent with a short instruction such as
{"text":"swap 100 USDC for ETH on Base"}. The response identifies the amount,
sell token, buy token, and chain. It does not fetch an executable quote or place a trade; use MCP,
the SDK, or the per-chain orderbook flow for execution.
What makes the flow agent-safe?
- The agent signs a typed, bounded order rather than an arbitrary transaction.
- The signed limit defines the worst acceptable execution.
- The receiver can be pinned to the owner to prevent output redirection.
- The SDK resolves non-canonical settlement domains on Ophis-operated chains.
- Ophis never receives or stores the signing key.
Does Ophis provide a crypto swap API for AI agents?
Yes, through three surfaces. The hosted MCP server covers token resolution, quoting, bounded-order construction, validation, and signed-order submission. The public Intent API parses natural-language swap requests but does not execute them. The @ophis/sdk provides chain-aware helpers for custom integrations.
Does an Ophis agent integration require an API key?
No. The hosted MCP server and public Intent API are keyless. Rate limits and endpoint-specific controls still apply, and the agent or user keeps custody of the signing key.
Can Ophis sign a trade for my agent?
No. Ophis never holds the agent key and never signs an order. The integration builds a bounded EIP-712 order with a hard limit price; the agent or its wallet signs locally, then submits the signed order.