The OIP glossary
What the concept is
OIP stands for Object Invocation Protocol. It is a way to call code objects by sending a plain web address.
An object is a named piece of code stored on the server. A key is the name that points to one object.
A capability is what one object can do when it runs. A token is a short string that proves you are allowed to run an object.
A tenant is one user or team that owns objects inside the system.
A dispatch is the act of sending a request that makes an object run. The route POST /api/dispatch {key, body} starts a dispatch. The route GET /api/dispatch?invoke=KEY&body=... also starts a dispatch.
A receipt is the proof that a dispatch happened. Every receipt lives at /api/dispatch?receipt=inv_ID. The ledger is the permanent list of all receipts.
REST stands for Representational State Transfer. It is the style of web addresses used by OIP.
CLI stands for Command Line Interface. It is a text program you run in a terminal to talk to OIP.
JSON stands for JavaScript Object Notation. It is a simple text format for sending data.
MCP stands for Model Context Protocol. MCP is an open standard that keeps an open session between a model and a server. The MCP server gives the model tools, resources, and prompts. OIP has no session; any model that can open a URL can call objects.
Why this build cares about it
Every term above appears in other OIP articles. A single glossary stops repeated explanations. It also makes the machine-native JSON easier to read.
How to see or use it live with curl against https://miscsubjects.com
You cannot fetch the glossary with one curl because it is a static page. You can fetch the article at the route /a/oip-glossary. You can test any term by running a dispatch. Example: curl -X POST https://miscsubjects.com/api/dispatch \ -H "Content-Type: application/json" \ -d '{"key":"oip-tap-go","body":{}}' This uses the exact route POST /api/dispatch. The response contains a receipt URL.
How it relates to MCP when relevant
MCP keeps a live session and lists tools the model can call. OIP uses one-shot URLs and receipts instead. No open connection is needed.
Where the proof lives
Every dispatch writes one row in the append-only ledger. The receipt at /api/dispatch?receipt=inv_ID shows the exact key, body, and result. These receipts are the only source of truth for the glossary terms.