New Runtime for developers and agents

Quickstart

Published records and ordinary public reads require no API key, login, payment, or sandbox account. Start with llms.txt, narrow the relevant collection, and retrieve only the detail records needed for the task. Optional paid compute products are advertised separately and always begin with an unsigned request.

curl -sS https://newruntime.com/llms.txt

curl -sS https://newruntime.com/patterns.json

curl -sS -H 'Accept: text/markdown' https://newruntime.com/

Contracts and discovery

The primary OpenAPI document covers the programmatic JSON, MCP, and paid compute surface. The separate route catalog describes the broader HTML, Markdown, text, and XML publication surface. The API catalog and MCP server card connect these descriptions without implying editorial or operational write access.

Free agent actions

Researching a URL found elsewhere? GET /agent-actions/contextualize.json?url=<https URL> (or the contextualize_url MCP tool) returns the published records that cite it, related records and patterns, its source-origin hub, and next steps. It is free and gives no coverage verdict; the paid prior-coverage check does.

Agents can also propose a source, report a correction with evidence, or leave a usage receipt: POST JSON to /agent-inbox/source, /agent-inbox/correction, or /agent-inbox/usage-receipt, or call submit_source, submit_correction, or submit_usage_receipt over MCP. Nothing is published directly. Submissions are reviewed weekly (Monday), accepted ones are credited in the record's weekly update, and /agent-inbox/submissions/<id>.json shows the status. Limits: 8 KiB per body, 30 submissions per client per 24 hours; a repeat within 24 hours returns the earlier submission.

curl -sS 'https://newruntime.com/agent-actions/contextualize.json?url=https%3A%2F%2Fgithub.com%2Fopenai%2Fcodex&task=release%20history'

curl -sS https://newruntime.com/agent-inbox/source \
  -H 'Content-Type: application/json' \
  --data '{"url":"https://vendor.example/launch","related_record":"patterns/agent-payments","reason":"Primary launch post the pattern does not cite yet.","agent":{"name":"Example Agent"}}'

Paid agent compute

Read payment-capabilities immediately before paying. Send the product request without PAYMENT-SIGNATURE first: validation, quota, and result preparation happen before the service returns a 402. Invalid, empty, and insufficient-evidence requests are not settled.

A sellable response returns PAYMENT-REQUIRED with fixed-price USDC rails, one short-lived server-priced EURC/WETH/cbBTC/wSOL rail, or one exact-direct native BNB/ETH/AVAX/POL/SOL rail. A buyer should enforce its own product, price, network, token, recipient, and spend policy. Native transfers must include the returned terms-hash data or memo and are released only after finality. A settled result can be replayed without another payment.

curl -sS https://newruntime.com/agent-payments/payment-capabilities

curl -sS https://newruntime.com/agent-payments/research-bundle-v2/volatile/weth-base -H 'Content-Type: application/json' --data '{"query":"agent payment protocols","max_sources":5,"known_stable_ids":[]}'

curl -sS https://newruntime.com/agent-payments/research-bundle-v2/native/bnb-bsc -H 'Content-Type: application/json' --data '{"query":"agent payment protocols","max_sources":5,"known_stable_ids":[]}'

curl -sS https://newruntime.com/agent-payments/research-bundle-v2 \
  -H 'Content-Type: application/json' \
  --data '{"query":"agent payment protocols","max_sources":5,"known_stable_ids":[]}'

curl -sS https://newruntime.com/agent-payments/prior-coverage \
  -H 'Content-Type: application/json' \
  --data '{"topic":"agent payment protocols","freshness_days":90}'

MCP transport

To add the server to Claude, Cursor, VS Code or Codex in one line, see /connect/.

The hosted MCP endpoint is POST /mcp using Streamable HTTP (POST /.well-known/mcp is the same endpoint). It exposes resources, resource templates, read-only tools (search_archive, get_record, contextualize_url, whats_new, what_changed, get_forecasts, list_agent_tasks, get_latest_metadox, get_topic_brief, get_submission_status, list_paid_tools), moderated submission tools (submit_source, submit_correction, submit_usage_receipt) that queue proposals for weekly review, and prompts that chain them: research_a_url, weekly_ai_engineering_brief, verify_a_claim. No tool edits or publishes a record; publication, approval, deployment, administration, private data, and authenticated user operations are not available.

Handshake-era initialize answers an unsupported requested protocol version with 2025-11-25 instead of an error, as the MCP specification requires; JSON-RPC batches of up to 10 messages are accepted from 2025-03-26 clients.

The enforced MCP limit is 60 requests per minute per observed client address, with a 256 KiB request-body limit and a five-second body timeout. A 429 response includes RateLimit fields and Retry-After.

curl -sS https://newruntime.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: server/discover' \
  --data '{"jsonrpc":"2.0","id":1,"method":"server/discover","params":{"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientInfo":{"name":"example","version":"1.0.0"},"io.modelcontextprotocol/clientCapabilities":{}}}}'

REST JSON limits

Public JSON routes enforce 120 requests per minute per observed client address. Successful responses include RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy. A 429 response uses application/problem+json and adds Retry-After. HTML and Markdown publication pages are not part of this REST bucket.

curl -sSI https://newruntime.com/topics.json | grep -Ei '^(ratelimit|retry-after|link):'

Errors and versions

HTTP-layer errors use RFC 9457 application/problem+json when JSON is requested. MCP protocol failures remain JSON-RPC errors. Missing canonical pages can also return short HTML or Markdown recovery documents while preserving the original status code.

The public JSON contract is versioned through the OpenAPI info.version field and schema_version fields in records. Additive fields may appear without removing existing fields. Incompatible changes require a new contract or schema version.

Deprecation and sunset policy

No public route or MCP protocol version is currently deprecated or scheduled for removal. Every public JSON response links this policy with rel=deprecation, but Deprecation and Sunset headers are intentionally absent until a concrete lifecycle event is scheduled.

A future incompatible removal will be announced here and in the substantive change feed. Affected responses will carry the RFC 9745 Deprecation header and a rel=deprecation Link. If an endpoint will become unavailable, it will also carry the RFC 8594 Sunset header. The normal migration window is at least 90 days between the announced deprecation date and sunset; urgent security, privacy, or legal risks may require a shorter window and will be documented explicitly.