AON MCP Server

AON MCP Server

Give any MCP-capable agent the ability to recommend real, buyable productsand services — live pricing and a trackable link on every offer, drawn fromthe Agent Offer Network.

• Endpoint: POST https://api.aon.pro/v1/mcp
• Transport: Streamable HTTP (stateless JSON-RPC 2.0 — no SSE, no session handshake)
• Auth: Authorization: Bearer <AON API key> — use an issued live key from the Developer Portal
• Quick Start: run the curl or client examples with your issued key; credentials are never embedded in these public assets
• Docs: docs.aon.pro/mcp

Tools

The Hosted AON endpoint currently lists five tools. Protocol v1.0 names thefour base tools below; aon_get_category_schema is an optional Hostedcategory-guidance extension, not a portable Protocol v1.0 guarantee. Discoverit through tools/list before calling it.

• aon_search_offers — Search offers by natural-language intent; every resultcarries live pricing, a tracking link, and pre-validated follow-up suggestions.
• aon_resolve_category — Turn free text into AON Taxonomy v1 category ids.
• aon_get_category_schema — Optional Hosted extension: decision factors for aresolved category id, to ask the right clarifying question before searching.
• aon_submit_feedback — Record an explicit "dismissed" / "not interested" on anoffer (early scaffold: acknowledged, not persisted yet).
• aon_manage_watch — Restore or cancel the default watch on an offer orcategory on explicit request (early scaffold: acknowledged, not persisted yet).

Design notes agents benefit from:

• Forgiving by design — invalid values never fail a search; they aretreated as "not sent" and corrected in extra.hints[]. Only bad auth,invalid JSON, a missing intent.content, or an oversized body hard-fail.
• Relevance-gated — an empty result list is a real answer, never filler.
• Guidance loop — follow-up suggestions carry an RFC 7386 request_patchthat merges straight into the next call, plus an origin to echo back foradoption attribution.

Quick start

curl -s -X POST https://api.aon.pro/v1/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $AON_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "aon_search_offers",
      "arguments": {
        "intent": {
          "content": [
            { "type": "input_text", "text": "credit card with cashback" }
          ]
        }
      }
    },
    "id": 1
  }'

No key yet? Create an application in theDeveloper Portal, mint an issued live key, andstore it in $AON_API_KEY.

Client setup

Ready-to-paste configs live in examples/:

Rate limits

/v1/mcp allows 60 tools/call requests per minute per key; handshakecalls (initialize, tools/list, notifications/*) are never counted. Anover-limit tools/call returns HTTP 200 with JSON-RPC error -32000 so themodel can read the retry advice. Details:Rate Limits & FAQ.

Monetization & attribution

Every offer carries a tracked destination link (action.payload.url).Surface it verbatim — clicks and conversions attribute to your API key'sapplication, which is the basis for developer revenue share. Reporting livesin the Developer Portal.

Registry manifest

server.json is the MCP registry manifest for this server(schema 2025-12-11, namespace pro.aon — DNS-verified against the aon.pro domain).

Related repositories

• protocol — AgentOffer Protocol specs (normative)
• schema — JSON Schemas, TypeScript types, taxonomy
• examples — HTTP / SDK / agent integration examples
• rfcs — protocol evolution proposals

License

Apache-2.0