Bezahlte Endpunkte für autonome Agenten. Abrechnung über x402 in USDC auf Base Mainnet.
POST /v1/webhook-inbox
Gives an agent without a reachable server a place to receive callbacks. create returns a public URL that accepts any POST, GET or PUT from a third party; poll returns the events that arrived since a cursor you carry forward, with headers, parsed body and arrival time. The inbox expires after at most seven days and holds at most 500 events, oldest dropped first. Reading requires the secret returned at creation. Do not point payment or authentication callbacks here: anyone who learns the URL can post to it, and stored bodies are readable with the secret alone.
0.005 USDC je Aufruf · MCP webhook_inbox
POST /v1/state-store
Key-value state for agents that need to survive between calls. Every write carries a time-to-live; the maximum is 30 days and there is no way to store something permanently. Values are opaque JSON up to 64 KB, at most 1000 live keys per namespace. Actions: set, get, list, delete. A get on a missing or expired key answers found=false, it is not an error. The namespace is a plain string chosen by the caller and is not authenticated — anyone who knows it can read it, so do not put secrets in it. Expired rows are removed on access, not on a timer, so a list can lag a few seconds behind the exact expiry moment.
0.002 USDC je Aufruf · MCP state_store
POST /v1/wakeup
Books a single POST to a URL you own, at a time you name, with a payload you supply. Delivery is retried up to five times with growing gaps and every attempt is recorded with its status. Lead time is between 10 seconds and 30 days, and at most 200 pending wakeups per target URL. The target must be a public https address: private, loopback and link-local addresses are refused, so this cannot be pointed at an internal network. Delivery is at-least-once and the time is a floor, not a guarantee — the dispatcher checks every 15 seconds, so expect a few seconds of lag. Actions: schedule, status, cancel, list.
0.002 USDC je Aufruf · MCP wakeup_schedule
POST /v1/job-runner
For work that outlives one HTTP response. You submit steps, each an HTTP request against a public address; the job is acknowledged at once and runs in the background, and the collected results are POSTed to your callback URL when finished. Every step reports its status, timing, response headers and body up to 256 KB, and a failing step never aborts the others. Price is 0.003 USDC per step, quoted before payment. Only http and https against public hosts are performed — private and loopback addresses are refused and no supplied code is ever executed. Steps run one after another with a 20 second cap each, so a 50-step job can take several minutes. Actions: submit, status, cancel.
0.003 USDC je Aufruf · MCP job_runner
POST /v1/file-vault
Takes a base64 file up to 25 MB and stores it for as long as you say, at most seven days. You get a download URL carrying a 32-byte token; whoever holds the link can fetch the file once or up to a limit you set, with no payment and no account. Price is 0.004 USDC per started megabyte, quoted before payment from the size you declare. Actions: store, status, delete. Anything expired is deleted with its contents, and a link is only as private as you keep it, so this is not a place for personal or secret material. Content is stored and served unchanged and is never inspected or scanned.
0.004 USDC je Aufruf · MCP file_vault
POST /v1/a2a-card-validate
Validates an Agent Card document against the A2A convention and returns findings by severity: error (the card is unusable as published), warning (works, but a consuming agent will guess), info (recommended field absent). Checked: the required fields name, description, url, version, capabilities and skills; that url is absolute and https; that every skill carries id, name, description and tags and that skill ids are unique; that declared securitySchemes use a known type and that every entry in security refers to a defined scheme; that input and output modes are declared; that streaming and pushNotifications are booleans. This endpoint does not fetch the card and never contacts the agent: it judges only the document handed to it, so a passing card is not proof that the endpoint is reachable or honest.
0.002 USDC je Aufruf · MCP a2a_card_validate
POST /v1/mcp-inspect
Performs the MCP handshake against a streamable-HTTP endpoint and then reads the catalogue: tools with their input schemas, resources with their URIs and mime types, and prompts with their arguments. Servers answering as an event stream are handled as well as plain JSON, and a session id is carried across calls. Only listing methods are sent — no tool of the inspected server is ever executed, nothing is written, and no resource contents are read. The target must be a public address; private and loopback addresses are refused. An unreachable or non-conforming server yields a reachable=false report with the reason, not an error.
0.005 USDC je Aufruf · MCP mcp_inspect
POST /v1/mcp-normalize
Takes a list of MCP tool definitions, as returned by tools/list on any number of servers, and rewrites them into one common form. Servers disagree on where the schema lives — inputSchema, input_schema, parameters, schema or arguments are all in use — and a consumer reading only one of them loses the others silently; every spelling is accepted and the one found is reported. For each tool the result carries a flat field list with type, required flag and description, a synthetic example call built from the schema, and the tool name normalised to snake_case. Name collisions across servers are detected and reported with the servers involved. The example call shows the shape only: values like "string" and 0 are placeholders and must never be sent to a live server. No network access happens here — only the definitions handed in are read.
0.002 USDC je Aufruf · MCP mcp_normalize
POST /v1/fallback-resolve
Searches the public x402 discovery catalogue for services able to replace a broken dependency. Give the failed URL and, better still, a short description of what it did and the fields you need back; matches are scored on overlap between your task words and the candidate name, description and path, then ordered by score and price. Every hit carries the reason it matched, its price in USDC, its network and when the catalogue last saw it. The endpoint that failed is excluded from its own replacement list. This reads a public index and never calls a candidate: a listed service is not proof that it works today, and the input schema of a replacement will differ, so treat the result as a shortlist to test, not a drop-in.
0.005 USDC je Aufruf · MCP fallback_resolve
POST /v1/task-quote-compare
Normalises offers that describe the same task in different shapes and ranks them. Each offer may carry a price, a delivery time, a list of capabilities and one or more delivery formats. You state which capabilities and formats the task requires; offers missing a required capability or format are marked ineligible and ranked last, never silently dropped. The ranking is a weighted score over price, speed and capability coverage, with weights you supply and which are echoed back. Every ranked entry carries the sub-scores it was built from, so the order can be recomputed by hand. Prices must already be in one currency: no conversion happens here, and a mixed-currency input is rejected rather than compared wrongly.
0.005 USDC je Aufruf · MCP task_quote_compare
POST /v1/result-consensus
Takes two to twelve answers and returns a field-by-field comparison. For JSON answers every leaf path is compared across responders: a path is agreed when all responders that supplied it carry the same value, conflicting when they differ, and partial when some omitted it. Numbers count as equal inside a relative tolerance you set. For plain-text answers the comparison is word-overlap similarity, which measures shared vocabulary and not meaning — two correct answers in different words will score low, and that is reported as low agreement, not as a contradiction. The result names a majority value per conflicting path together with how many responders backed it. This endpoint does not decide who is right: it has no ground truth and no model, it only shows where the answers part company.
0.002 USDC je Aufruf · MCP result_consensus