Skip to main content

AI platform submission checklist

Code-side discovery is wired up — /.well-known/x402, /.well-known/ai-plugin.json, /.well-known/mcp.json, and /openapi.json all serve. The remaining step is human-driven submission to each platform's directory. This page tracks where to submit and what each registry needs.

Already automatic (no submission needed)​

These directories scrape /.well-known/* and /openapi.json on a schedule — Jintel shows up without a form:

  • agentic.market — reads /openapi.json + /.well-known/x402
  • x402scan — reads /.well-known/x402
  • AgentCash directory — reads /openapi.json (validate locally with npx -y @agentcash/discovery@latest discover https://jintel.ai)

Manual submissions​

Anthropic MCP registry​

Anthropic curates a remote-MCP server directory accessible from Claude. Submission is via PR / form against the registry — see Anthropic's current guidance at modelcontextprotocol.io for the live submission link.

What to include:

  • Server name: Jintel
  • Endpoint: https://jintel.ai/mcp (Streamable HTTP)
  • Local install: npx -y @yojinhq/jintel-mcp
  • Description: "Finance intelligence MCP server — market data, regulatory, sanctions, macro, news, technicals."
  • Auth: Bearer jk_live_… or x402 pay-per-query
  • Docs: docs.jintel.ai/sdk/mcp

OpenAI GPT Store​

Build a Custom GPT pointed at https://jintel.ai/openapi.json, then submit it to the GPT Store from chat.openai.com. OpenAI's submission flow lives inside the ChatGPT UI; see help.openai.com for the current path.

Cursor MCP registry​

Cursor maintains an MCP discovery list inside the IDE. Submission process is fluid — see cursor.com for current instructions. Send the same payload as the Anthropic registry above.

Google Gemini Extensions / Gems​

Submission flow changes frequently. The OpenAPI URL https://jintel.ai/openapi.json is the artifact; follow Google's current process at ai.google.dev.

Pre-submission validation​

Before clicking submit on any of the above, run:

# Confirms /.well-known/x402 + /openapi.json parse cleanly
npx -y @agentcash/discovery@latest discover https://jintel.ai

# Confirms ai-plugin manifest parses
curl -s https://jintel.ai/.well-known/ai-plugin.json | jq .

# Confirms MCP descriptor parses
curl -s https://jintel.ai/.well-known/mcp.json | jq .

# Confirms OpenAPI is valid 3.1
curl -s https://jintel.ai/openapi.json | jq '.openapi'

All four should return cleanly. If agentcash discover reports anything beyond the optional WELLKNOWN_NOT_FOUND info note, fix that first.