miscsubjects.com
Object Invocation Protocol · protocol specification

OIP vs LangChain Tools

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

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-vs-langchain-tools
**Machine bundle:** https://miscsubjects.com/api/articles/oip-vs-langchain-tools/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.

Introduction to OIP vs LangChain Tools

OIP (Object Invocation Protocol) is a protocol specification that defines a work object as a unit of invocation, whereas LangChain tools are code-bound abstractions that operate on data.

Comparison of OIP and LangChain Tools

OIP operates on data-bound directory rows, whereas LangChain tools are bound to code.

Receipt Rule

The receipt rule for OIP is that every invocation appends to the ledger and returns a receipt at /api/dispatch?receipt=inv_ID.

Conformance Rule

The conformance rule for OIP is that every object must be invoked using the POST /api/dispatch or GET /api/dispatch?invoke=KEY&body=... route, and must return a receipt at /api/dispatch?receipt=inv_ID.

Example

An example of using OIP to invoke an object is to use the curl command to send a POST request to https://miscsubjects.com/api/dispatch with a JSON body containing the key and body of the object.

1
version
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 OIP vs LangChain Tools. 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-vs-langchain-tools · 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 23:06 · 0 tok · virtual-oip
verify chain →
Live ledger · 50 payloads · 20 turns
recent activity · inspect
delivery.delivered blooio · 2026-07-03 04:01
delivery.delivered blooio · 2026-07-03 04:01
PROTOCOL_RUN dispatch · 2026-07-03 04:01 · t_zh1rquhg
PROTOCOL_RUN dispatch · 2026-07-03 04:01 · t_zh1rquhg
delivery.delivered blooio · 2026-07-03 04:01
delivery.delivered blooio · 2026-07-03 04:01
view full ledger & cards →
OIP REST + ledger
read GET /a/oip-vs-langchain-tools · GET /api/articles/oip-vs-langchain-tools · GET /api/articles/oip-vs-langchain-tools/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…