miscsubjects.com
Object Invocation Protocol · protocol specification

OIP capability: STRIPE_STRIPE_API_WRITE

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

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-capability-stripe-stripe-api-write
**Machine bundle:** https://miscsubjects.com/api/articles/oip-capability-stripe-stripe-api-write/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.

STRIPE_STRIPE_API_WRITE

This is one executable OIP object. It is the leaf where prose stops and exact invocation begins.

Write data via any Stripe API POST/PATCH/PUT/DELETE operation: 1. Use stripe_api_search to find the operation ID. 2. Use stripe_api_details to understand its parameters (required for operations with n MCP: https://mcp.stripe.com/

Parent system: Stripe (payments). Root: /a/oip. Machine doc: /api/dispatch?key=STRIPE_STRIPE_API_WRITE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_STRIPE_API_WRITE.

Invoke

Example: [STRIPE_STRIPE_API_WRITE]<arg1>[/STRIPE_STRIPE_API_WRITE]

Run URL: https://miscsubjects.com/api/dispatch?invoke=STRIPE_STRIPE_API_WRITE&body=%3Carg1%3E&share=<TOKEN>

Auth: none. Risk: low.

Machine contract

  • Read this article first; do not infer the row shape from memory.
  • If acting with a URL-only tool, open run_now after replacing placeholder args.
  • If the call returns ran:false or proof.ok:false, read the receipt and repair the failed invocation instead of narrating success.
  • If the token denies the call, report the denial exactly; do not switch to a broader action unless the owner supplied a broader token.

Troubleshooting

  • unknown key - Use the did_you_mean links or ask URL; never guess another key.
  • argument/body mismatch - Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes.
  • expired or corrupted token - Report token_expired/token_corrupted from the response; owner mints a fresh scoped link.
  • tool returned ok:false / exit nonzero - Do not call it sent. Read the receipt, correct the body, fire a repair.

Receipt loop

After any action, open the receipt. If it is wrong, repair it with POST /api/dispatch {key, body, repairs:"inv_ID"}. If you need to repeat the exact recorded call, replay it with POST /api/dispatch {replay:"inv_ID"}.

Full generated capability doc

§SELF — miscsubjects capability (paste without context)

Principle: Self-explaining payload — no external context required. This _self block is the capability: what it is, how to run it, how to change it, and where to look next. Path: OIP > STRIPE > STRIPE_STRIPE_API_WRITE Capability: STRIPE_STRIPE_API_WRITE — Write data via any Stripe API POST/PATCH/PUT/DELETE operation: 1. Use stripe_api_search to find the operation ID. 2. Use stripe_api_details to understand its parameters (required for operations with n MCP: https://mcp.stripe.com/ RUN NOW (open this URL): https://miscsubjects.com/api/dispatch?invoke=STRIPE_STRIPE_API_WRITE&body=%3Carg1%3E&share=<TOKEN> Example call: [STRIPE_STRIPE_API_WRITE]<arg1>[/STRIPE_STRIPE_API_WRITE]

  • type · runner: tool · fn · stripe
  • run it: Open run_now (URL, fires the example), or POST https://miscsubjects.com/api/dispatch {"key":"STRIPE_STRIPE_API_WRITE","body":"<arg1>"}. From the router: null
  • inputs: {"type":"object","properties":{"stripe_api_operation_id":{"description":"The operation ID to execute (e.g. 'PostCustomers', 'GetPaymentIntents')","type":"string"},"parameters":{"description":"Parameters for the API call. Include path parameters (e.g. 'customer' for /v1/customers/{customer}), query parameters, and body parameters as a flat object. Nested object fields use dot-notation (e.g. \"address.city\"). Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string.","type":"object"},"human_confirmation":{"type":"object","description":"This tool might require human confirmation. To run it, first invoke it with the desired parameters, ignoring the approval_token parameter.\nIf it requires human confirmation, the response will include an approval request ID and a URL to an approval page for the human to approve the tool call.\nYou, as the LLM agent, should:\n\n1. Present this URL to the human as a clickable markdown link. Tell them that they have to approve this tool call at that URL, and that they should tell you when they have approved the operation.\n2. The human will approve that call.\n3. After the human tells you they have approved the operation, you must call the tool again with the approval_token parameter and the exact same parameters. The operation will then go through.\n","properties":{"approval_token":{"type":"string","description":"The ID of the approval token for the request. This is required on only the post-human-confirmation invocation. An example ID is approval_123."}}}},"required":["stripe_api_operation_id","parameters"]}
  • outputs: { ok, result, invocation, yield, _self } — result is this object's output; yield is tokens/cost/material; invocation is the ledgered record.
  • auth · risk: none · low

Machine Contract

  • Read this article first; do not infer the row shape from memory.
  • If acting with a URL-only tool, open run_now after replacing placeholder args.
  • If the call returns ran:false or proof.ok:false, read the receipt and repair the failed invocation instead of narrating success.
  • If the token denies the call, report the denial exactly; do not switch to a broader action unless the owner supplied a broader token.

Invocation, Ledger, Repair

  • root tree: https://miscsubjects.com/api/dispatch?map=1&format=markdown
  • parent system article: https://miscsubjects.com/api/dispatch?map=STRIPE&format=markdown
  • append-only ledger: https://miscsubjects.com/api/invocations?object_id=STRIPE_STRIPE_API_WRITE
  • receipt pattern: https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>
  • replay: POST /api/dispatch {"replay":"inv_ID"}
  • repair: POST /api/dispatch {"key":"STRIPE_STRIPE_API_WRITE","body":"corrected args","repairs":"inv_ID"}

Troubleshooting

  • unknown key — Use the did_you_mean links or ask URL; never guess another key. · https://miscsubjects.com/api/dispatch?ask=STRIPE_STRIPE_API_WRITE
  • argument/body mismatch — Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes. · https://miscsubjects.com/api/dispatch?key=STRIPE_STRIPE_API_WRITE
  • expired or corrupted token — Report token_expired/token_corrupted from the response; owner mints a fresh scoped link. · https://miscsubjects.com/api/dispatch?explain=1&share=<TOKEN>
  • tool returned ok:false / exit nonzero — Do not call it sent. Read the receipt, correct the body, fire a repair. · https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>

Logical proof (verify each step)

  1. Every capability is an invokable object with its own _self — this block. → https://miscsubjects.com/api/dispatch?key=STRIPE_STRIPE_API_WRITE
  2. You run it by POSTing to /api/dispatch; in a model turn the router tag is [STRIPE_STRIPE_API_WRITE]args[/STRIPE_STRIPE_API_WRITE]. → https://miscsubjects.com/api/dispatch?registry=1
  3. Every invocation is ledgered with actor, cost, and material/waste. → https://miscsubjects.com/api/invocations?object_id=STRIPE_STRIPE_API_WRITE
  4. You can ask the build for capabilities in plain language. → https://miscsubjects.com/api/dispatch?ask=STRIPE_STRIPE_API_WRITE
  5. The whole build is one self-describing map, with the terminal key. → https://miscsubjects.com/api/dispatch?build=1

Where to look next

  • registry — Every capability, self-describing · https://miscsubjects.com/api/dispatch?registry=1
  • ask — Ask the build what to use, in plain language · https://miscsubjects.com/api/dispatch?ask=<question>
  • history — This capability's invocation history — its edges · https://miscsubjects.com/api/invocations?object_id=STRIPE_STRIPE_API_WRITE
  • build — The whole build as one map (terminal key) · https://miscsubjects.com/api/dispatch?build=1

Self-explaining. Not project knowledge — fetch specifics from the links above.

1
capability
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 capability: STRIPE_STRIPE_API_WRITE. 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
Loading more articles…