aiagentscity-com MCP API
The Mcp API from aiagentscity-com — 2 operation(s) for mcp.
The Mcp API from aiagentscity-com — 2 operation(s) for mcp.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/aiagentscity-com:aiagentscity-com-mcp-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: AgentLedger MCP API
version: 0.4.7
x-guidance: 'AgentLedger is per-agent AI spend tracking with ENFORCED budget caps. Two ways in, both machine-only. (1) FREE, no wallet: POST /start mints a workspace_key (shown once) with no signup and no card — GET /start only renders the form and does NOT mint. Claim an agent with the key in the body of POST /v1/track, set a cap with POST /v1/budget, then route traffic through /proxy/{provider}/... so an over-budget call is refused with 402 BEFORE the provider is contacted. (2) PAID, no human: POST /v1/billing/x402 with a wallet-signed x402 payment mints a workspace bound to the paying wallet. NOTE: a workspace_key claims NEW agents; an agent_secret writes to an existing one. Plain POST /v1/track can reject the ledger write that would cross a cap but cannot un-spend a charge that already happened — only the proxy/wrapper path stops money.'
tags:
- name: MCP
paths:
/mcp/.well-known/oauth-authorization-server:
get:
summary: Oauth Discovery Absent
description: 'Answer the OAuth discovery probes honestly, instead of 404ing them.
An MCP client that wants authenticated transport walks RFC 9728 / RFC 8414
discovery before it will connect. Measured 2026-09-16 in /data/metrics.jsonl:
150 such probes 404''d, including /mcp/-relative variants. A 404 reads as
"discovery is broken"; it does not read as "no auth here".
This deployment has no auth layer at all — MCP here is deliberately open
(`claude mcp add --transport http agent-ledger https://aiagentscity.com/mcp/`
needs no login). The correct answer is therefore an explicit empty discovery
document: it tells the client no authorization server exists, so it should
proceed unauthenticated, and it stops the 404 loop.
Returning a fake authorization_server here would be worse than the 404: it
would send a client to an endpoint that cannot issue tokens.'
operationId: oauth_discovery_absent_mcp__well_known_oauth_authorization_server_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- MCP
/mcp/.well-known/oauth-protected-resource:
get:
summary: Oauth Discovery Absent
description: 'Answer the OAuth discovery probes honestly, instead of 404ing them.
An MCP client that wants authenticated transport walks RFC 9728 / RFC 8414
discovery before it will connect. Measured 2026-09-16 in /data/metrics.jsonl:
150 such probes 404''d, including /mcp/-relative variants. A 404 reads as
"discovery is broken"; it does not read as "no auth here".
This deployment has no auth layer at all — MCP here is deliberately open
(`claude mcp add --transport http agent-ledger https://aiagentscity.com/mcp/`
needs no login). The correct answer is therefore an explicit empty discovery
document: it tells the client no authorization server exists, so it should
proceed unauthenticated, and it stops the 404 loop.
Returning a fake authorization_server here would be worse than the 404: it
would send a client to an endpoint that cannot issue tokens.'
operationId: oauth_discovery_absent_mcp__well_known_oauth_protected_resource_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- MCP
x-service-info:
docs:
llms: /llms.txt
x-products:
- id: trustscan
x-slot: trust
x-direction: outward
x-connect:
mcp: https://aiagentscity.com/mcp/trustscan
paid_call: POST https://aiagentscity.com/api/x402/trustscan/npm
human: https://aiagentscity.com/trust-scan
tagline: Scan before you trust
free_proof: POST /api/trustscan/npm returns registry facts + a typosquat screen for any package, unauthenticated — the same check is payable per call over x402 without the rate limit; remote deep scans are path-scoped to the host
- id: agent-watch
x-slot: trust
x-direction: outward
x-connect:
mcp: https://aiagentscity.com/mcp/agent-watch
paid_call: POST https://aiagentscity.com/api/x402/agent-watch/probe
human: https://aiagentscity.com/agent-watch
tagline: Is this agent or MCP server real and still behaving?
free_proof: aw_health + aw_census MCP tools are open reads — live census data, no auth
- id: perimeter-watch
x-slot: trust
x-direction: outward
x-connect:
mcp: https://aiagentscity.com/mcp/perimeter-watch
human: https://aiagentscity.com/perimeter-watch
tagline: Is your endpoint still what it claims — checked from the outside?
free_proof: free browser snapshot — https://entradox.github.io/perimeter-watch-site/
- id: benefits-city
x-slot: outcome
x-direction: outward
x-connect:
mcp: https://aiagentscity.com/benefits/mcp
human: https://aiagentscity.com/benefits
tagline: Verified offer records — will this action actually pay?
free_proof: search_bonuses / get_bonus MCP tools return hand-verified records with source URLs — no auth
- id: cited
x-slot: outcome
x-direction: outward
x-connect:
mcp: https://aiagentscity.com/mcp/cited
human: https://aiagentscity.com/cited
tagline: Prove the claim that AI recommends you — verbatim evidence
free_proof: free browser scan — https://entradox.github.io/cited-site/
- id: agent-ledger
x-slot: outcome
x-direction: spine
x-connect:
mcp: https://aiagentscity.com/mcp/
rest: https://aiagentscity.com/v1/
install: npx @aiagentscity/setup ledger
human: https://aiagentscity.com/agent-ledger
tagline: Metered, capped, receipted agent spend — proof of what every cent bought
free_proof: POST /start mints a free workspace (3 agents, every rail) — no signup, no card
- id: workbench-kit
x-slot: trust+outcome
x-direction: inward
x-connect:
install: npx @aiagentscity/setup workbench
human: https://aiagentscity.com/workbench
tagline: Frame, gate, and close-receipt every agent task — proof of what your agents did
free_proof: the whole kit is free and runs fully offline — `wb verify <receipt_id>` recomputes a close receipt against the local ledger
x-frame:
frame: trust-and-outcome
tagline: 'The trust-and-outcome clearing layer for the agent economy: before an agent acts, it verifies the counterparty; after it acts, it proves the result.'
questions:
trust: Before an agent acts — can it trust the counterparty?
outcome: After an agent acts — did it work?
directions:
outward: verifies counterparties outside your fleet
spine: the receipts rail every instrument writes through
inward: verifies your own fleet's work
parked: []