{"slug":"oip-cloudflare-pages","title":"Cloudflare Pages","body":"## What is Cloudflare Pages\nCloudflare Pages is a service that helps deploy and manage web applications.\nIt is a platform that allows users to host and serve their web content.\n\n## Why OIP cares about Cloudflare Pages\nOIP (Object Invocation Protocol) cares about Cloudflare Pages because it uses Cloudflare Pages to deploy and manage its web application.\nThis allows OIP to serve its content to users in a fast and reliable way.\n\n## How to see or use Cloudflare Pages live\nTo see Cloudflare Pages in action, you can visit https://miscsubjects.com.\nYou can use the `curl` command to test the API endpoints, such as `POST /api/dispatch` or `GET /api/dispatch?invoke=KEY&body=...`.\nFor example, you can use the following command to invoke an object: `curl -X POST -H 'Content-Type: application/json' -d '{\"key\":\"OBJECT_KEY\",\"body\":\"OBJECT_BODY\"}' https://miscsubjects.com/api/dispatch`.\n\n## Comparison to MCP\nCloudflare Pages is different from MCP (Model Context Protocol) because it does not require a persistent session.\nMCP 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.\nIn contrast, Cloudflare Pages uses plain URLs and does not require a session.\n\n## Proof and receipts\nThe proof of deployment and management of web applications using Cloudflare Pages can be found in the OIP ledger and receipts.\nYou can access the ledger and receipts by visiting `/api/dispatch?receipt=inv_ID`, where `inv_ID` is the invocation ID.\nFor more information on OIP ledger and receipts, see [/a/oip-ledger-receipts](/a/oip-ledger-receipts).\n## Latest clarity reviews (live)\n\nFresh 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.\n\n- 2026-07-03 02:46 · model `@cf/meta/llama-3.3-70b-instruct-fp8-fast` · NEEDS WORK · JSON 8/10 · English 9/10 · zero-context human 7/10\n  - gaps named: OIP protocol details; Cloudflare Pages integration\n\nHow 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.","register":"oip_protocol","tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","dynamic"],"style":{"accent":"#16324f","measure":860},"claims":[{"id":"oip-c1","tier":"system","text":"The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.","who_claims":"system/oip_articles","source_ids":["oip-s3","oip-s4"]},{"id":"oip-c2","tier":"system","text":"The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.","who_claims":"system/oip_articles","source_ids":["oip-s1"]},{"id":"oip-c3","tier":"system","text":"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.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s3"]},{"id":"oip-c4","tier":"system","text":"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.","who_claims":"system/oip_articles","source_ids":["oip-s2"]},{"id":"oip-c5","tier":"system","text":"OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s5"]}],"sources":[{"id":"oip-s1","type":"protocol","title":"BUILD_SPEC object invocation path","url":"https://miscsubjects.com/api/file/docs/BUILD_SPEC.md","summary":"Defines directory rows, dispatch, ledger, and the escalation path for changing the build.","quote":"Run anything: POST https://miscsubjects.com/api/dispatch {key, body}","claim_ids":["oip-c2"],"link_status":"ok","hash":"oipbuildspec0001"},{"id":"oip-s2","type":"protocol","title":"Object Invocation Protocol spec","url":"https://miscsubjects.com/api/file/docs/OIP.md","summary":"Defines OIP surfaces, invariant loop, receipt/replay/repair, and invocation envelopes.","quote":"identify, explain, invoke, ledger, yield","claim_ids":["oip-c3","oip-c4","oip-c5"],"link_status":"ok","hash":"oipspec00000002"},{"id":"oip-s3","type":"protocol","title":"Live OIP capability tree","url":"https://miscsubjects.com/api/dispatch?map=1&format=markdown","summary":"Public recursive capability tree.","quote":"root > shelf > system article > capability article > receipt","claim_ids":["oip-c1","oip-c3"],"link_status":"ok","hash":"oipmap0000000002"},{"id":"oip-s4","type":"protocol","title":"Directory row documentation","url":"https://miscsubjects.com/api/dispatch?key=OIP_TREE&format=markdown","summary":"Capability articles are generated from live rows.","quote":"Machine Contract","claim_ids":["oip-c1"],"link_status":"ok","hash":"oiprow0000000003"},{"id":"oip-s5","type":"protocol","title":"Invocation ledger","url":"https://miscsubjects.com/api/invocations","summary":"Append-only invocation records and receipt links.","quote":"invocations","claim_ids":["oip-c5"],"link_status":"ok","hash":"oipinvocations0005"}],"prov":{"model":"system/oip_articles","action":"generate"}}