Install Jentic One Beta

Connect the New Runtime public JSON and MCP API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the New Runtime public JSON and MCP API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnewruntime.com%2Fnewruntime" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnewruntime.com%2Fnewruntime" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with New Runtime public JSON and MCP API.

List and read AI-industry signals, patterns, topic hubs, field notes, capability deltas, and structural shifts by slug

Read a system dossier and its release timeline, or a project blueprint, as structured JSON

Contextualize an outside https URL against published records, related patterns, and its source hub for free

Submit a source, a correction with a problem of outdated, unsupported, contradicted, or other, or a usage receipt to the moderated agent inbox and check its moderation status

GET STARTED

Start building with New Runtime public JSON and MCP API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use New Runtime public JSON and MCP API for, with concrete tasks.

★ Research agent grounding AI-industry answers

A research agent asked about a new AI tool or model wants structured, sourced records rather than a general web search. Through Jentic the agent searches for 'contextualize a URL against AI-industry research', loads the New Runtime contextualize operation with its input schema, and passes the url and an optional task. It gets back records citing that URL, related records and patterns, and its source hub, then reads individual signals or system dossiers by slug for detail.

Call GET /agent-actions/contextualize.json with url 'https://github.com/openai/codex' and task 'summarize coverage', then read the first related record with GET /signals/{slug}.json

Verifying a claim before repeating it

Before an agent repeats an AI-industry rumour, it checks it. The rumour-check tool searches X over the last 7 days with reposts and replies excluded, counts independent authors and trusted voices, and looks for an official statement, returning a verdict such as official_source_found, corroborated, discussed_unconfirmed, or no_discussion. The unsigned request validates input for free and the check runs after x402 payment verification.

Send POST /agent-payments/rumor-check with claim 'Vendor X is deprecating its v1 API next month', review the 402 quote, and retry with a PAYMENT-SIGNATURE only if the user approves

Feeding corrections back to the publisher

When an agent finds a published claim that a newer source contradicts, it can report it instead of silently ignoring it. The correction operation takes the record, the claim, a problem such as outdated or contradicted, an evidence_url, and the submitting agent, and queues it for weekly moderated review without changing the site. The submission's moderation status can be checked later by id.

Call POST /agent-inbox/correction with record, claim, problem 'outdated', evidence_url, and agent, then poll GET /agent-inbox/submissions/{submission_id}.json

Key Endpoints

68 endpoints — the new runtime public json api publishes new runtime's ai-industry research as typed, read-only json: raw signals, patterns, topic hubs, field notes, capability deltas, structural shifts, system dossiers with release timelines, project blueprints, and learn guides, each listable and readable by slug.

METHOD

PATH

DESCRIPTION

GET

/signals.json

List raw signals

GET

/systems/{slug}.json

Read a system dossier

GET

/systems/{slug}/releases.json

Read a system release timeline

GET

/agent-actions/contextualize.json

Contextualize an outside URL

POST

/agent-payments/rumor-check

Check an AI-industry rumour

POST

/agent-payments/primary-source

Find the primary source behind a claim

POST

/agent-inbox/correction

Submit a correction

GET

/feed.json

Read the JSON Feed

GET

/signals.json

List raw signals

GET

/systems/{slug}.json

Read a system dossier

GET

/systems/{slug}/releases.json

Read a system release timeline

GET

/agent-actions/contextualize.json

Contextualize an outside URL

POST

/agent-payments/rumor-check

Check an AI-industry rumour

POST

/agent-payments/primary-source

Find the primary source behind a claim

POST

/agent-inbox/correction

Submit a correction

GET

/feed.json

Read the JSON Feed

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring New Runtime by hand means mapping dozens of static JSON routes, telling free reads apart from x402 paid routes that answer an unsigned POST with a 402 quote, and pacing calls against the RateLimit fields. Through Jentic you install once, import New Runtime from the API Directory, and your agent calls it with no key to configure.

Permission scoping

New Runtime puts the record slug in the URL path, but the bound that matters is by operation and path prefix: a rule can hold your agent to the free GET reads. You choose the operations it may call, so the paid routes under /agent-payments and inbox submissions are not included unless you add them.

Credential isolation

New Runtime declares no API credential, so there is no key for your Jentic One instance to hold for the free routes. Paid routes are settled per call with an x402 PAYMENT-SIGNATURE rather than an account key.

Intent-based discovery

Agents search Jentic by intent such as 'check an AI rumour' or 'read a system dossier', and Jentic returns the matching New Runtime operation with its input schema so the agent picks the right route among 68.

FAQs

Specific to using New Runtime public JSON and MCP API through Jentic.

What authentication does the New Runtime API use?

The OpenAPI spec declares no security schemes, and every operation is public. Free reads need no account or API key. The paid tools also need no account: the first unsigned POST validates the request and, for a sellable result, returns an HTTP 402 x402 quote, and you retry with a PAYMENT-SIGNATURE header to settle it.

Can I read the release history of an AI system with the New Runtime API?

Yes. GET /systems.json lists system dossiers, GET /systems/{slug}.json returns one structured dossier with private commands and credentials excluded, and GET /systems/{slug}/releases.json returns its release timeline.

What are the rate limits for the New Runtime API?

The spec states that public static JSON reads enforce 120 requests per minute and return live RateLimit fields in the response, so an agent can pace itself from those headers.

Is there a New Runtime MCP server?

Yes - New Runtime hosts a read-only MCP endpoint at POST /mcp. You can also connect the API directly through Jentic: your agent gets the full 68-endpoint surface from the spec without loading another server's tool definitions into its context, and your rules decide which operations the agent may call, including whether it can reach the paid routes.

How do I contextualize a URL with New Runtime through Jentic?

Import New Runtime from the API Directory in your Jentic One instance; there is no key to add. Your agent searches for 'contextualize a URL', loads GET /agent-actions/contextualize.json, and passes the https url plus an optional task. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the New Runtime API?

Yes. Write a rule that allows only the GET operations, and the agent can read every research record and contextualize URLs but cannot call the x402 paid tools under /agent-payments or post to the agent inbox. Every call it makes is logged.

New Runtime public JSON and MCP API

AI ReadinessAI-Aware (B+)70/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingContent Managementnone68 EndpointsREST

For Agents

Read New Runtime's AI-industry signals, patterns, shifts, and system dossiers as JSON, contextualize a URL against them, submit moderated corrections, and call x402 paid tools for primary sources and rumour checks.

Use for: List the latest AI-industry signals, Get the release timeline for a system dossier, Find what New Runtime has published about this URL, Check whether this AI rumour has an official source

Not supported: Does not provide general web search, live market data, or posting to social networks. Use for reading New Runtime's AI-industry research and its verification tools only.

The New Runtime public JSON API publishes New Runtime's AI-industry research as typed, read-only JSON: raw signals, patterns, topic hubs, field notes, capability deltas, structural shifts, system dossiers with release timelines, project blueprints, and Learn guides, each listable and readable by slug. It also exposes the site's own machine-readership data, such as bot traffic aggregates, crawler journeys, and a discovery graph, and a free operation that contextualizes an outside URL against published records. A moderated agent inbox accepts sources, corrections, and usage receipts, and optional x402 paid tools find the primary source behind a claim, check an AI-industry rumour against X discussion, test for prior coverage, and build research bundles.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

71%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: B+Signals: 4

47%

Description Coverage

Coverage of descriptions across API elements.

79%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

91%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the New Runtime public JSON and MCP API to your agent

Capabilities

Start building with New Runtime public JSON and MCP API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

New Runtime public JSON and MCP API

Jentic AI Readiness Score

New Runtime public JSON and MCP API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness