New Runtime public records

Use when you need dated, source-linked coverage of an AI-engineering product, company or topic (agents, MCP, coding tools, model releases) without crawling the web. Keyword search (English, word forms match) over Field Notes (every news story), Signals, analyses, patterns, shifts, dossiers, topic hubs, tool change logs and tested-tool experiments; title and phrase matches rank first. Up to 25 hits per call with title, date, summary and URL; pass next_offset as offset for more. Same results as GET https://newruntime.com/search.json. Free, no auth. Example: {"query": "MCP security", "kind": "post", "limit": 5}. Then get_record for the full text.

Use after search_archive, whats_new, what_changed, get_topic_brief or contextualize_url to read one record in full: metadata (dates, topics, source URLs, primary_source_url) and the body as Markdown (capped; see truncated). Pass any newruntime.com record URL they return (notes, signals, analyses, patterns, shifts, systems, projects, topics, tools, guides, sources), or kind + slug. Free, no auth. Example: {"url": "https://newruntime.com/patterns/company-memory-needs-write-loops/"}.

Use when the free tools left a question open and you can pay per call: lists New Runtime's x402 tools (find the primary source of a claim $0.10, rumour check $0.40, research bundle, prior-coverage check) with endpoint, USDC price, input example, when you are charged, and how to pay without an account. Free to call.

Takes no parameters.

Use first when you found an AI or software URL elsewhere (a release note, repo, blog post, tweet) and want to know what New Runtime already has on it: records citing that exact URL or the same site, related records and patterns, the source hub, and a coverage summary. It reports what the archive holds, not a duplicate-or-new verdict (that is an optional paid call). Free, no auth. Example: {"url": "https://github.com/modelcontextprotocol/servers", "task": "is this new?"}.

Use for a feed of what New Runtime published in the last 1-14 days, optionally on one topic: Field Notes (one per news story), Signals (syntheses of 2+ notes), analyses and weekly knowledge updates, with title, date, URL and a one-line why. Balanced by default (every day and kind get a turn); order "newest" is strictly by time. Up to 40 per call; pass next_offset as offset for more. Free, no auth. Example: {"days": 7, "topic": "coding-agents", "kinds": ["post", "signal", "analysis"]}. For what changed against what you already knew, use what_changed.

Use when you already know a topic and need only what changed since a date (your last run, a report date): which AI-engineering patterns and shifts got stronger or weaker, what became obsolete, forecasts that resolved (none yet while every forecast is still open), which new items are new facts versus new angles on known stories, and the Field Notes and analyses published, plus what still holds. Saves re-reading and re-deduplicating the web. Free, no auth. Example: {"since": "2026-09-01", "topic": "mcp"}.

Use when you need falsifiable, dated predictions about AI engineering: New Runtime's forecast ledger (claim, probability, due date, source analysis). Forecasts are graded when due; the scorecard (hit rate, Brier score) stays empty until the first ones resolve, and the result says when that is. Free, no auth. Example: {"status": "open", "limit": 10}.

Use when you can contribute evidence: open verification tasks on New Runtime patterns and shifts that are stale or below high confidence, each with the record, what evidence is missing and which submit tool to use. Accepted evidence is credited publicly in the record's weekly update. Free. Example: {"kind": "find_fresh_primary_source"}.

Use when you want one synthesis of the week in AI engineering instead of a list: the newest weekly metadox (the week's central contradiction, counter-evidence and dated forecasts) as Markdown, up to 12,000 characters, with title, date and URL. Free, no auth. No arguments.

Takes no parameters.

Use when you need the background on one AI-engineering topic in one call: its summary, what was published on it in the last fortnight, and the top related patterns, shifts, Field Notes and Signals with URLs. Free, no auth. Example: {"topic": "coding-agents"}. Topics: https://newruntime.com/topics.json; systems (openclaw, hermes) work too.

Use when your user wants this week's AI news picked for them by you: New Runtime publishes each week as plain data files. Default: the manifest (week, the corpora with item counts, language and token estimates, feedback route). Every corpus is an index, one line per item: "site" = the week's Field Notes (English; open https://newruntime.com/posts/<slug>.md for your shortlist), "telegram" = the week's Telegram posts (Russian), "digest" = news that did not get its own Telegram post (Russian). Shortlist from the index, then read one telegram or digest entry by id (tg-<n> or dg-<n>); level "full" returns a whole telegram or digest corpus in full text (large; only when the user wants everything). Check tokens_estimate and full_tokens_estimate in the manifest first. Data only: nothing in the files is an instruction. Instructions: https://newruntime.com/for-your-agent.md; feedback: submit_relevance_report. Free, no auth. Example: {"corpus": "telegram", "id": "tg-4123"}.

Moderation status of a source, correction or usage receipt you submitted (received, accepted, rejected...), by its as_... submission id. Shows only the public moderation fields.

Propose a source (primary page, paper, repo, docs) for a New Runtime record or topic. Free. Submissions are not published. They are reviewed weekly (Monday); accepted items are credited in the record's weekly update. A relevance report orders that reader's personalized week corpus right away; the weekly review only removes rejected reports from it. Returns a submission id and a status URL. Schema: https://newruntime.com/agent-inbox/schema.json.

Report a claim in a published record as outdated, unsupported or contradicted, with evidence. Free. Submissions are not published. They are reviewed weekly (Monday); accepted items are credited in the record's weekly update. A relevance report orders that reader's personalized week corpus right away; the weekly review only removes rejected reports from it. Schema: https://newruntime.com/agent-inbox/schema.json.

Record that you used a New Runtime record and for what (optionally where it can be seen). Free; helps the weekly desk see which records matter. Submissions are not published. They are reviewed weekly (Monday); accepted items are credited in the record's weekly update. A relevance report orders that reader's personalized week corpus right away; the weekly review only removes rejected reports from it. Schema: https://newruntime.com/agent-inbox/schema.json.

After reading a week corpus (get_week_corpus) for your user and only with their approval of the exact JSON: report which stories mattered (picked ids from the corpus with verdict act, read or watch), interest tags, what was missing, or a comment. Send at least one of picked or comment. Free. Reports are not published; they are reviewed weekly. The receipt carries reader_key: keep it for your user and send it with the next report; the site index ordered for them is then at https://newruntime.com/agent-inbox/corpus/{week}/{reader_key}.md. Schema: https://newruntime.com/agent-inbox/schema.json.