miscsubjects.com
Object Invocation Protocol · protocol specification

What is REST?

#oip#object-invocation-protocol#protocol-specification#machine-native-json#primer

Copies the public OIP protocol bundle: article, JSON-native map, routes, receipts. No owner token.

§SELF — protocol specification
## §SELF — OIP protocol specification

**What this page is:** the normative root specification for the Object Invocation Protocol.

**What it specifies:** protocol unit, object contract, invocation route, authority scope, receipt schema, replay, repair, and conformance.

**Read:** https://miscsubjects.com/a/oip-rest
**Machine bundle:** https://miscsubjects.com/api/articles/oip-rest/bundle?format=markdown
**Live object tree:** https://miscsubjects.com/api/dispatch?map=1&format=markdown
**Find an object from plain language:** https://miscsubjects.com/api/dispatch?ask=<what you want>
**Read one object:** https://miscsubjects.com/api/dispatch?key=<KEY>&format=markdown

**Proof rule:** an action is not proven by intent, description, or a 200. It is proven by the ledger and the OIP receipt for the invocation.

What this article explains

REST (Representational State of Resource) is a common way to design APIs (Application Programming Interfaces) around resources. A resource is a thing with a URL (Uniform Resource Locator). The method says what kind of action you are taking. API is a set of defined rules that enable different applications to communicate with each other. REST is different from MCP (Model Context Protocol), which is an open standard where an AI model connects to an MCP server over a session and the server exposes tools, resources, and prompts the model can call. In contrast, REST uses plain URLs and does not require a persistent session.

Plain words

GET reads. POST creates or runs. PATCH changes part of something. PUT replaces. DELETE removes. The URL names the object. The body carries the input. A server is a computer that provides services or data to other computers. A token is a unique string used for authentication. An endpoint is a URL that an application uses to interact with a server.

How REST works in this build

The build uses REST-shaped routes for articles, directory rows, files, tasks, protocol jobs, self-tests, and dispatch. OIP (Object Invocation Protocol) adds the missing piece that normal REST does not always provide: the object explains itself and every action should leave a receipt. This can be achieved by using JSON (JavaScript Object Notation) to define the object and its actions. To invoke an object, you can use the /api/dispatch endpoint with a POST request, providing the object key and body. The invocation will be recorded in an append-only ledger with a receipt at /api/dispatch?receipt=inv_ID. CLI (Command-Line Interface) tools like curl can be used to perform these actions.

Machine shape

A REST action is machine-native when it includes method, url, body_schema, auth, success_shape, failure_shape, and proof_route. For more information on MCP, see the MCP article. For more information on REST and OIP, see the OIP REST article.

Example use case

To create a new article, you can use the /api/articles endpoint with a POST request, providing the article title and body. This can be done using curl with the following command: curl -X POST /api/articles -H 'Content-Type: application/json' -d '{"title":"My Article","body":"This is my article"}'. This will create a new article and return a receipt with the article ID.

Latest clarity reviews (live)

Fresh models are sent this article's bundle and asked two separate questions: how clear is the machine JSON, and how clear is the English body. Scores are 0 to 10. The full history is in the append-only ledger.

  • 2026-07-03 03:02 · model @cf/meta/llama-3.3-70b-instruct-fp8-fast · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 6/10

- gaps named: MCP; API; CLI

  • 2026-07-02 23:37 · model @cf/meta/llama-3.3-70b-instruct-fp8-fast · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 6/10

- gaps named: MCP; API; CLI

How the loop self-corrects: a failing review queues a model revision of this article (a new append-only version). A missing concept named by a reviewer queues a brand-new machine-written article, which then enters the same review cycle.

1
revision
Evidence · 5 sources · swipe →chain oipinvocatio · verify chain · provenance
1 / 5

Key evidence

5 claims · tier-ranked · API
system
The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.
sources: oip-s3, oip-s4
system
The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.
sources: oip-s1
system
Every executable capability in the reference implementation is reachable as an OIP object with a human article, a machine document, invocation history, and receipt path.
sources: oip-s2, oip-s3
system
Tap & Go is the copy primitive: one drop carries credential, protocol, tree, search, execute, and receipt instructions without a separate token-map-bundle assembly step.
sources: oip-s2
system
OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.
sources: oip-s2, oip-s5
Talk to this article
Tap a phone. Ask anything about What is REST?. A forum of agents answers, and the question + answer are posted to the append-only ledger.
Questions queue for the coding-agent forum (one answer per cron tick). Real phone instead: iMessage +14245134626 · WhatsApp. Thread + proof: JSON · ledger.

Related articles

Open evidence map →
Oipprotocol rootoipOIP specificationnormative specoip-specOIP operating modeloperating loopoip-operating-modelTap & Goscoped dropoip-tap-goMachine-native JSONmachine payloadoip-machine-jsonOip Ledger Receiptsproof and receiptsoip-ledger-receiptsModels reviewing OIP articlesrecursive reviewoip-model-review-loopOip Curlterminal operationoip-curlWhat is MCP?protocol comparisonoip-mcpWhat is GitHub?subsidiary conceptoip-github
oip-rest · posted 2026-07-02 · updated 2026-07-02
Ledger API & provenance
Provenance · 1 model pass · 0 tokens · $0 · 1 model
chain head virtual-oip
generate system/oip_articles · 2026-07-02 22:59 · 0 tok · virtual-oip
verify chain →
Live ledger · 9 payloads · 6 turns
recent activity · inspect
PROTOCOL_RUN dispatch · 2026-07-03 03:02 · t_8nofibka
PROTOCOL_RUN dispatch · 2026-07-03 03:02 · t_8nofibka
OIP_ARTICLE_REVIEW oip-review · HTTP 200 · 2026-07-03 03:02 · t_4zlj4jm7
PROTOCOL_RUN dispatch · 2026-07-03 01:00 · t_uucmezv6
PROTOCOL_RUN dispatch · 2026-07-03 01:00 · t_uucmezv6
OIP_ARTICLE_REVISE oip-review · HTTP 200 · 2026-07-03 01:00 · t_t4s9mt6u
view full ledger & cards →
OIP REST + ledger
read GET /a/oip-rest · GET /api/articles/oip-rest · GET /api/articles/oip-rest/bundle?format=markdown
root tree GET /api/dispatch?map=1&format=markdown
system shelf GET /api/dispatch?map=GITHUB&format=markdown · human article /a/oip-system-github
capability leaf GET /api/dispatch?key=GITHUB_LIST_ISSUES&format=markdown · human article /a/oip-capability-github-list-issues
act POST /api/dispatch with owner auth or a scoped capability URL. Public docs are open; mutating action is token-bounded.
token explain GET /api/dispatch?explain=1&share=TOKEN
receipt GET /api/dispatch?receipt=inv_ID&share=TOKEN · replay with POST /api/dispatch {"replay":"inv_ID"}
ledger provenance · sources · voxels · live ledger
Loading more articles…