{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"oip-system-net","title":"OIP system: NET","body":"## NET\n\nA generated article for one OIP shelf. It lists every operation in this API/CLI/MCP/device/model/core subsystem, links each leaf article, and gives the ledger path for proof.\n\nThis page is the operating article for one build subsystem. It is generated from live directory rows. If a task belongs to this subsystem, scan the operations below, open the matching capability article, run only the exact object named there, and verify by receipt.\n\nKind: `core`. Capabilities: `5`. Machine system map: [/api/dispatch?map=NET&format=markdown](https://miscsubjects.com/api/dispatch?map=NET&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip).\n\n## Operations\n\n### NET_SEARCH\nSearch the web and get back titles, urls and snippets. The request leaves from the operator's residential IP and bandwidth (this Mac on Starlink), not a datacenter, so results are not shaped by a cloud IP and sites that block datacenters still answer.\nUse when: you need live web results and want them fetched from a real residential connection\nArguments: `$1 = the query`.\nHuman article: [/a/oip-capability-net-search](https://miscsubjects.com/a/oip-capability-net-search). Machine doc: [?key=NET_SEARCH&format=markdown](https://miscsubjects.com/api/dispatch?key=NET_SEARCH&format=markdown). Invocation history: [/api/invocations?object_id=NET_SEARCH](https://miscsubjects.com/api/invocations?object_id=NET_SEARCH).\n\n### NET_FETCH\nDo a raw HTTP request to any URL from the operator's IP and return the status, final url, content type and body. Use for APIs, JSON, files and pages that answer over plain HTTP.\nUse when: you need the bytes of a URL fetched from a residential connection\nArguments: `$1 = the url`.\nHuman article: [/a/oip-capability-net-fetch](https://miscsubjects.com/a/oip-capability-net-fetch). Machine doc: [?key=NET_FETCH&format=markdown](https://miscsubjects.com/api/dispatch?key=NET_FETCH&format=markdown). Invocation history: [/api/invocations?object_id=NET_FETCH](https://miscsubjects.com/api/invocations?object_id=NET_FETCH).\n\n### NET_SCRAPE\nOpen a URL in a real browser on the operator's machine (JavaScript runs), and return the title, clean visible text, links, and optionally a screenshot. Use for sites that need rendering or that block datacenters.\nUse when: a page needs a real browser and a residential IP\nArguments: `$1 = the url`.\nHuman article: [/a/oip-capability-net-scrape](https://miscsubjects.com/a/oip-capability-net-scrape). Machine doc: [?key=NET_SCRAPE&format=markdown](https://miscsubjects.com/api/dispatch?key=NET_SCRAPE&format=markdown). Invocation history: [/api/invocations?object_id=NET_SCRAPE](https://miscsubjects.com/api/invocations?object_id=NET_SCRAPE).\n\n### NET_IP\nReport the public IP, ISP/org, and city the operator's internet is leaving from right now (this Mac on Starlink). Proof of which line web ops run over.\nUse when: confirm the egress before a run\nArguments: `none`.\nHuman article: [/a/oip-capability-net-ip](https://miscsubjects.com/a/oip-capability-net-ip). Machine doc: [?key=NET_IP&format=markdown](https://miscsubjects.com/api/dispatch?key=NET_IP&format=markdown). Invocation history: [/api/invocations?object_id=NET_IP](https://miscsubjects.com/api/invocations?object_id=NET_IP).\n\n### NET_LINE\nReads the line the tools run on: the egress IP and network, and when the machine sits behind a Starlink terminal, the dish itself over its local API: uptime, latency to the point of presence, ping drop rate, downlink and uplink throughput, obstruction fraction, GPS lock, hardware and software version, alerts. Read-only. Location is refused by Starlink policy on consumer plans and is reported as such.\nUse when: before promising a job that needs the line, or to explain a slow or failed web call\nArguments: `none`.\nHuman article: [/a/oip-capability-net-line](https://miscsubjects.com/a/oip-capability-net-line). Machine doc: [?key=NET_LINE&format=markdown](https://miscsubjects.com/api/dispatch?key=NET_LINE&format=markdown). Invocation history: [/api/invocations?object_id=NET_LINE](https://miscsubjects.com/api/invocations?object_id=NET_LINE).\n","register":"oip_protocol","tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","system"],"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"}}