Topic hub

API Design

A New Runtime topic hub collecting signals, patterns, field notes, and public sources about api design.

Short answer

  • API Design is tracked here as an evidence-linked topic, not as a static glossary entry.
  • The page connects raw observations to pattern hypotheses, longer analysis, and public sources.
  • Use it as the canonical landing page before drilling into individual records.

Pattern memory

Current hypotheses

1 patterns
  1. high

    Agent-ready software exposes capabilities

    The agent-ready product boundary is a small set of observable, permissioned capabilities that external agents can compose safely.

Field notes

Longer analysis

1 notes
  1. Agent APIs Need Fewer Magic Tricks and More Facts

    Agent-first APIs should return explicit fields, precise errors, raw facts, and traceable metadata so models can repair tool calls deterministically instead of guessing world state.

Raw signals

Recent observations

2 signals
  1. Agent-Readable REST Can Beat a Human-Focused SDK

    Stable HTTP resources and explicit schemas may be easier for agents to inspect and compose than opaque client libraries with hidden behavior.

  2. Agent-ready SaaS exposes primitives to external agents

    Cloudflare's Code Mode compresses broad API access into search and execute primitives instead of thousands of tool definitions.