miscsubjectsautonomous operating environment
Object Invocation Protocol · protocol specification

OIP system: Stripe (payments)

Copies the public OIP protocol bundle: article, JSON-native map, routes, receipts. No owner token.

§SELF — protocol specification · traversal JSON in-band
## §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-system-stripe
**This page as JSON:** https://miscsubjects.com/api/articles/oip-system-stripe
**Machine bundle:** https://miscsubjects.com/api/articles/oip-system-stripe/bundle?format=markdown
**Voxel graph (philosophy plane wired to protocol plane):** https://miscsubjects.com/api/articles/oip/voxels
**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.

A 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.

This 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.

Kind: api. Capabilities: 68. Machine system map: /api/dispatch?map=STRIPE&format=markdown. Root: /a/oip.

Operations

STRIPE_PUBLIC_KEY_GET

Return env var by name. Use ONLY for publishable values (e.g. STRIPE_PUBLIC_KEY). Never for secret keys Use when: you need to stripe public key get Arguments: none. Human article: /a/oip-capability-stripe-public-key-get. Machine doc: ?key=STRIPE_PUBLIC_KEY_GET&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PUBLIC_KEY_GET.

STRIPE_CATALOG_SYNC

Pull active products + prices from Stripe and upsert into D1.stripe_catalog Use when: refresh local SKU cache Arguments: none. Human article: /a/oip-capability-stripe-catalog-sync. Machine doc: ?key=STRIPE_CATALOG_SYNC&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CATALOG_SYNC.

STRIPE_SKUS_LIST

List cached SKUs (product name, brand, opaque_id, prices summary). Run STRIPE_CATALOG_SYNC first to refresh. Use when: When you need to list cached SKUs (product name, brand, opaque_id, prices summary). Run STRIPE_CATALOG_SYNC first to refresh. Human article: /a/oip-capability-stripe-skus-list. Machine doc: ?key=STRIPE_SKUS_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_SKUS_LIST.

STRIPE_SKUS_BY_NAME

Find cached SKU by name pattern $1 (LIKE %$1%). Returns matching products + prices. Use when: When you need to find cached SKU by name pattern. Human article: /a/oip-capability-stripe-skus-by-name. Machine doc: ?key=STRIPE_SKUS_BY_NAME&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_SKUS_BY_NAME.

STRIPE_PEPTIDES

Return the active peptide product inventory from the stripe_catalog cache. Lists name, brand=esh, opaque_id, and the price tiers per product (24 prices each = starter/standard/advanced × 1mo/3mo/6mo/12mo × sub/onetime). Use when the user asks for the peptide list, the SKU list, or what is for sale. Use when: When you need to return the active peptide product inventory from the stripe_catalog cache. Human article: /a/oip-capability-stripe-peptides. Machine doc: ?key=STRIPE_PEPTIDES&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PEPTIDES.

STRIPE_READ

Read anything from Stripe through one door. Twenty-four read operations — balance, charges, customers, invoices, payouts, payment intents, prices, products, subscriptions, refunds, events — selected by the op argument. This account is in live mode. Use when: Any Stripe read. Arguments: op (required) — Which read to perform · selector (optional) — The op's first argument · limit (optional) — invoice_items_list only: the page size, 1 to 100. Human article: /a/oip-capability-stripe-read. Machine doc: ?key=STRIPE_READ&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_READ.

STRIPE_WRITE

Stripe WRITE unified entrypoint — GATED Use when: only after the owner says "go ahead and <verb>". POST/PATCH/DELETE on Stripe Arguments: $1=op, $2..$N=positional args. Human article: /a/oip-capability-stripe-write. Machine doc: ?key=STRIPE_WRITE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_WRITE.

STRIPE_SEARCH_STRIPE_DOCUMENTATION

Search the Stripe documentation for the given question and language. It takes two arguments: - question (str): The user question to search an answer for in the Stripe documentation. - language (str, o. Use when: When you need to search the Stripe documentation for the given question and language. Human article: /a/oip-capability-stripe-search-stripe-documentation. Machine doc: ?key=STRIPE_SEARCH_STRIPE_DOCUMENTATION&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_SEARCH_STRIPE_DOCUMENTATION.

STRIPE_GET_STRIPE_ACCOUNT_INFO

This will get the account info for the logged in Stripe account. Use when: When you need to this will get the account info for the logged in Stripe account. Human article: /a/oip-capability-stripe-get-stripe-account-info. Machine doc: ?key=STRIPE_GET_STRIPE_ACCOUNT_INFO&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_GET_STRIPE_ACCOUNT_INFO.

STRIPE_CREATE_REFUND

This tool will refund a payment intent in Stripe. It takes three arguments: - payment_intent (str): The ID of the payment intent to refund. - amount (int, optional): The amount to refund in currency m. Use when: When you need to this tool will refund a payment intent in Stripe. Human article: /a/oip-capability-stripe-create-refund. Machine doc: ?key=STRIPE_CREATE_REFUND&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CREATE_REFUND.

STRIPE_SEARCH_STRIPE_RESOURCES

This tool can be used to search for specific Stripe resources using a custom Stripe query syntax. It is only able to search for the following resources: customers, payment_intents, charges, invoices,. Use when: When you need to this tool can be used to search for specific Stripe resources using a custom Stripe query syntax. Human article: /a/oip-capability-stripe-search-stripe-resources. Machine doc: ?key=STRIPE_SEARCH_STRIPE_RESOURCES&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_SEARCH_STRIPE_RESOURCES.

STRIPE_FETCH_STRIPE_RESOURCES

Retrieve Stripe object details by ID. IMPORTANT: Only call this tool after search_stripe_resources is called to get specific object IDs. Do not use this tool to discover or search for objects. This to. Use when: When you need to retrieve Stripe object details by ID. Human article: /a/oip-capability-stripe-fetch-stripe-resources. Machine doc: ?key=STRIPE_FETCH_STRIPE_RESOURCES&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_FETCH_STRIPE_RESOURCES.

STRIPE_STRIPE_IMPLEMENTATION_PLANNER

Stripe payment integration planner. Use this tool to help users accept payments, sell products online, set up billing, or build any Stripe integration. Call this BEFORE writing code when the user want. Use when: When you need to stripe payment integration planner. Human article: /a/oip-capability-stripe-stripe-implementation-planner. Machine doc: ?key=STRIPE_STRIPE_IMPLEMENTATION_PLANNER&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_STRIPE_IMPLEMENTATION_PLANNER.

STRIPE_SEND_STRIPE_MCP_FEEDBACK

Submit feedback from user or agent about Stripe's MCP server tools. Valid: "the search tool returned irrelevant results", "I wish there was a tool for X" Invalid: Stripe API complaints, AI model issue. Use when: When you need to submit feedback from user or agent about Stripe's MCP server tools. Human article: /a/oip-capability-stripe-send-stripe-mcp-feedback. Machine doc: ?key=STRIPE_SEND_STRIPE_MCP_FEEDBACK&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_SEND_STRIPE_MCP_FEEDBACK.

STRIPE_STRIPE_API_SEARCH

Search for Stripe API operations by keyword. Returns matching operations with their HTTP method, path, summary, and top-level parameter names with types. Does not include parameter descriptions, enum. Use when: When you need to search for Stripe API operations by keyword. Human article: /a/oip-capability-stripe-stripe-api-search. Machine doc: ?key=STRIPE_STRIPE_API_SEARCH&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_STRIPE_API_SEARCH.

STRIPE_STRIPE_API_DETAILS

Get detailed parameter information for a specific Stripe API operation. Provide the stripe_api_operation_id from stripe_api_search results to see all path, query, and body parameters with their types,. Use when: When you need to get detailed parameter information for a specific Stripe API operation. Human article: /a/oip-capability-stripe-stripe-api-details. Machine doc: ?key=STRIPE_STRIPE_API_DETAILS&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_STRIPE_API_DETAILS.

STRIPE_STRIPE_API_READ

Read data from any Stripe API GET operation: 1. Use stripe_api_search to find the operation ID. 2. Use stripe_api_details to understand its parameters (required for operations with nested object field. Use when: When you need to read data from any Stripe API GET operation: 1. Human article: /a/oip-capability-stripe-stripe-api-read. Machine doc: ?key=STRIPE_STRIPE_API_READ&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_STRIPE_API_READ.

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. Use when: When you need to write data via any Stripe API POST/PATCH/PUT/DELETE operation: 1. Human article: /a/oip-capability-stripe-stripe-api-write. Machine doc: ?key=STRIPE_STRIPE_API_WRITE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_STRIPE_API_WRITE.

STRIPE_ACCOUNT

Http row invoking target GET https://api.stripe.com/v1/account. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/account. Human article: /a/oip-capability-stripe-account. Machine doc: ?key=STRIPE_ACCOUNT&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_ACCOUNT.

STRIPE_BALANCE

Http row invoking target GET https://api.stripe.com/v1/balance. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/balance. Human article: /a/oip-capability-stripe-balance. Machine doc: ?key=STRIPE_BALANCE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_BALANCE.

STRIPE_BALANCE_TX_LIST

Http row invoking target GET https://api.stripe.com/v1/balance_transactions?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/balance_transactions?limit=$1. Human article: /a/oip-capability-stripe-balance-tx-list. Machine doc: ?key=STRIPE_BALANCE_TX_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_BALANCE_TX_LIST.

STRIPE_CUSTOMERS_LIST

Http row invoking target GET https://api.stripe.com/v1/customers?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/customers?limit=$1. Human article: /a/oip-capability-stripe-customers-list. Machine doc: ?key=STRIPE_CUSTOMERS_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CUSTOMERS_LIST.

STRIPE_CUSTOMER_GET

Http row invoking target GET https://api.stripe.com/v1/customers/$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/customers/$1. Human article: /a/oip-capability-stripe-customer-get. Machine doc: ?key=STRIPE_CUSTOMER_GET&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CUSTOMER_GET.

STRIPE_CUSTOMER_SEARCH

Http row invoking target GET https://api.stripe.com/v1/customers/search?query=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/customers/search?query=$1. Human article: /a/oip-capability-stripe-customer-search. Machine doc: ?key=STRIPE_CUSTOMER_SEARCH&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CUSTOMER_SEARCH.

STRIPE_CUSTOMER_CREATE

Form:email=$1&name=$2&phone=$3. Use when: When you need to form:email=$1&name=$2&phone=$3. Human article: /a/oip-capability-stripe-customer-create. Machine doc: ?key=STRIPE_CUSTOMER_CREATE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CUSTOMER_CREATE.

STRIPE_CUSTOMER_UPDATE

Form:email=$2&name=$3&phone=$4. Use when: When you need to form:email=$2&name=$3&phone=$4. Human article: /a/oip-capability-stripe-customer-update. Machine doc: ?key=STRIPE_CUSTOMER_UPDATE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CUSTOMER_UPDATE.

STRIPE_CUSTOMER_DELETE

Http row invoking target DELETE https://api.stripe.com/v1/customers/$1. Use when: When you need to http row invoking target DELETE https://api.stripe.com/v1/customers/$1. Human article: /a/oip-capability-stripe-customer-delete. Machine doc: ?key=STRIPE_CUSTOMER_DELETE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CUSTOMER_DELETE.

STRIPE_PRODUCTS_LIST

Http row invoking target GET https://api.stripe.com/v1/products?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/products?limit=$1. Human article: /a/oip-capability-stripe-products-list. Machine doc: ?key=STRIPE_PRODUCTS_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PRODUCTS_LIST.

STRIPE_PRODUCT_GET

Http row invoking target GET https://api.stripe.com/v1/products/$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/products/$1. Human article: /a/oip-capability-stripe-product-get. Machine doc: ?key=STRIPE_PRODUCT_GET&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PRODUCT_GET.

STRIPE_PRODUCT_CREATE

Form:name=$1&description=$2. Use when: When you need to form:name=$1&description=$2. Human article: /a/oip-capability-stripe-product-create. Machine doc: ?key=STRIPE_PRODUCT_CREATE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PRODUCT_CREATE.

STRIPE_PRICES_LIST

Http row invoking target GET https://api.stripe.com/v1/prices?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/prices?limit=$1. Human article: /a/oip-capability-stripe-prices-list. Machine doc: ?key=STRIPE_PRICES_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PRICES_LIST.

STRIPE_PRICE_GET

Http row invoking target GET https://api.stripe.com/v1/prices/$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/prices/$1. Human article: /a/oip-capability-stripe-price-get. Machine doc: ?key=STRIPE_PRICE_GET&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PRICE_GET.

STRIPE_PRICE_CREATE

Form:product=$1&unit_amount=$2&currency=$3. Use when: When you need to form:product=$1&unit_amount=$2&currency=$3. Human article: /a/oip-capability-stripe-price-create. Machine doc: ?key=STRIPE_PRICE_CREATE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PRICE_CREATE.

STRIPE_INVOICES_LIST

Http row invoking target GET https://api.stripe.com/v1/invoices?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/invoices?limit=$1. Human article: /a/oip-capability-stripe-invoices-list. Machine doc: ?key=STRIPE_INVOICES_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICES_LIST.

STRIPE_INVOICE_GET

Http row invoking target GET https://api.stripe.com/v1/invoices/$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/invoices/$1. Human article: /a/oip-capability-stripe-invoice-get. Machine doc: ?key=STRIPE_INVOICE_GET&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_GET.

STRIPE_INVOICE_CREATE

Form:customer=$1&collection_method=send_invoice&days_until_due=$2&description=$3. Use when: When you need to form:customer=$1&collection_method=send_invoice&days_until_due=$2&description=$3. Human article: /a/oip-capability-stripe-invoice-create. Machine doc: ?key=STRIPE_INVOICE_CREATE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_CREATE.

STRIPE_INVOICE_UPDATE

Form:description=$2. Use when: When you need to form:description=$2. Human article: /a/oip-capability-stripe-invoice-update. Machine doc: ?key=STRIPE_INVOICE_UPDATE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_UPDATE.

STRIPE_INVOICE_FINALIZE

Http row invoking target POST https://api.stripe.com/v1/invoices/$1/finalize. Use when: When you need to http row invoking target POST https://api.stripe.com/v1/invoices/$1/finalize. Human article: /a/oip-capability-stripe-invoice-finalize. Machine doc: ?key=STRIPE_INVOICE_FINALIZE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_FINALIZE.

STRIPE_INVOICE_SEND

Http row invoking target POST https://api.stripe.com/v1/invoices/$1/send. Use when: When you need to http row invoking target POST https://api.stripe.com/v1/invoices/$1/send. Human article: /a/oip-capability-stripe-invoice-send. Machine doc: ?key=STRIPE_INVOICE_SEND&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_SEND.

STRIPE_INVOICE_PAY

Http row invoking target POST https://api.stripe.com/v1/invoices/$1/pay. Use when: When you need to http row invoking target POST https://api.stripe.com/v1/invoices/$1/pay. Human article: /a/oip-capability-stripe-invoice-pay. Machine doc: ?key=STRIPE_INVOICE_PAY&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_PAY.

STRIPE_INVOICE_VOID

Http row invoking target POST https://api.stripe.com/v1/invoices/$1/void. Use when: When you need to http row invoking target POST https://api.stripe.com/v1/invoices/$1/void. Human article: /a/oip-capability-stripe-invoice-void. Machine doc: ?key=STRIPE_INVOICE_VOID&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_VOID.

STRIPE_INVOICE_MARK_UNCOLLECTIBLE

Http row invoking target POST https://api.stripe.com/v1/invoices/$1/mark_uncollectible. Use when: When you need to http row invoking target POST https://api.stripe.com/v1/invoices/$1/mark_uncollectible. Human article: /a/oip-capability-stripe-invoice-mark-uncollectible. Machine doc: ?key=STRIPE_INVOICE_MARK_UNCOLLECTIBLE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_MARK_UNCOLLECTIBLE.

STRIPE_INVOICE_DELETE

Http row invoking target DELETE https://api.stripe.com/v1/invoices/$1. Use when: When you need to http row invoking target DELETE https://api.stripe.com/v1/invoices/$1. Human article: /a/oip-capability-stripe-invoice-delete. Machine doc: ?key=STRIPE_INVOICE_DELETE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_DELETE.

STRIPE_INVOICE_ITEMS_LIST

Http row invoking target GET https://api.stripe.com/v1/invoiceitems?customer=$1&limit=$2. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/invoiceitems?customer=$1&limit=$2. Human article: /a/oip-capability-stripe-invoice-items-list. Machine doc: ?key=STRIPE_INVOICE_ITEMS_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_ITEMS_LIST.

STRIPE_INVOICE_ITEM_CREATE

Form:customer=$1&amount=$2&currency=$3&description=$4. Use when: When you need to form:customer=$1&amount=$2&currency=$3&description=$4. Human article: /a/oip-capability-stripe-invoice-item-create. Machine doc: ?key=STRIPE_INVOICE_ITEM_CREATE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_ITEM_CREATE.

STRIPE_INVOICE_ITEM_DELETE

Http row invoking target DELETE https://api.stripe.com/v1/invoiceitems/$1. Use when: When you need to http row invoking target DELETE https://api.stripe.com/v1/invoiceitems/$1. Human article: /a/oip-capability-stripe-invoice-item-delete. Machine doc: ?key=STRIPE_INVOICE_ITEM_DELETE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE_ITEM_DELETE.

STRIPE_CHARGES_LIST

Http row invoking target GET https://api.stripe.com/v1/charges?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/charges?limit=$1. Human article: /a/oip-capability-stripe-charges-list. Machine doc: ?key=STRIPE_CHARGES_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CHARGES_LIST.

STRIPE_CHARGE_GET

Http row invoking target GET https://api.stripe.com/v1/charges/$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/charges/$1. Human article: /a/oip-capability-stripe-charge-get. Machine doc: ?key=STRIPE_CHARGE_GET&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CHARGE_GET.

STRIPE_PI_LIST

Http row invoking target GET https://api.stripe.com/v1/payment_intents?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/payment_intents?limit=$1. Human article: /a/oip-capability-stripe-pi-list. Machine doc: ?key=STRIPE_PI_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PI_LIST.

STRIPE_PI_GET

Http row invoking target GET https://api.stripe.com/v1/payment_intents/$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/payment_intents/$1. Human article: /a/oip-capability-stripe-pi-get. Machine doc: ?key=STRIPE_PI_GET&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PI_GET.

STRIPE_PI_CREATE

Form:amount=$1&currency=$2&customer=$3&description=$4. Use when: When you need to form:amount=$1&currency=$2&customer=$3&description=$4. Human article: /a/oip-capability-stripe-pi-create. Machine doc: ?key=STRIPE_PI_CREATE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PI_CREATE.

STRIPE_PAYMENT_LINKS_LIST

Http row invoking target GET https://api.stripe.com/v1/payment_links?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/payment_links?limit=$1. Human article: /a/oip-capability-stripe-payment-links-list. Machine doc: ?key=STRIPE_PAYMENT_LINKS_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PAYMENT_LINKS_LIST.

STRIPE_PAYMENT_LINK_CREATE

Form:line_items0][price]=$1&line_items[0][quantity]=$2. Use when: When you need to form:line_items[0][price]=$1&line_items[0][quantity]=$2. Human article: [/a/oip-capability-stripe-payment-link-create. Machine doc: ?key=STRIPE_PAYMENT_LINK_CREATE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PAYMENT_LINK_CREATE.

STRIPE_SUBSCRIPTIONS_LIST

Http row invoking target GET https://api.stripe.com/v1/subscriptions?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/subscriptions?limit=$1. Human article: /a/oip-capability-stripe-subscriptions-list. Machine doc: ?key=STRIPE_SUBSCRIPTIONS_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_SUBSCRIPTIONS_LIST.

STRIPE_SUBSCRIPTION_GET

Http row invoking target GET https://api.stripe.com/v1/subscriptions/$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/subscriptions/$1. Human article: /a/oip-capability-stripe-subscription-get. Machine doc: ?key=STRIPE_SUBSCRIPTION_GET&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_SUBSCRIPTION_GET.

STRIPE_SUBSCRIPTION_CANCEL

Http row invoking target DELETE https://api.stripe.com/v1/subscriptions/$1. Use when: When you need to http row invoking target DELETE https://api.stripe.com/v1/subscriptions/$1. Human article: /a/oip-capability-stripe-subscription-cancel. Machine doc: ?key=STRIPE_SUBSCRIPTION_CANCEL&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_SUBSCRIPTION_CANCEL.

STRIPE_PAYOUTS_LIST

Http row invoking target GET https://api.stripe.com/v1/payouts?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/payouts?limit=$1. Human article: /a/oip-capability-stripe-payouts-list. Machine doc: ?key=STRIPE_PAYOUTS_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PAYOUTS_LIST.

STRIPE_PAYOUT_GET

Http row invoking target GET https://api.stripe.com/v1/payouts/$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/payouts/$1. Human article: /a/oip-capability-stripe-payout-get. Machine doc: ?key=STRIPE_PAYOUT_GET&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PAYOUT_GET.

STRIPE_REFUNDS_LIST

Http row invoking target GET https://api.stripe.com/v1/refunds?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/refunds?limit=$1. Human article: /a/oip-capability-stripe-refunds-list. Machine doc: ?key=STRIPE_REFUNDS_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_REFUNDS_LIST.

STRIPE_REFUND_CREATE

Form:charge=$1&amount=$2. Use when: When you need to form:charge=$1&amount=$2. Human article: /a/oip-capability-stripe-refund-create. Machine doc: ?key=STRIPE_REFUND_CREATE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_REFUND_CREATE.

STRIPE_EVENTS_LIST

Http row invoking target GET https://api.stripe.com/v1/events?limit=$1. Use when: When you need to http row invoking target GET https://api.stripe.com/v1/events?limit=$1. Human article: /a/oip-capability-stripe-events-list. Machine doc: ?key=STRIPE_EVENTS_LIST&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_EVENTS_LIST.

STRIPE_LH_CHARGES

Stripe charges on the loop.health account. $1 = how many (max 100). Use when: payment reconciliation, disputes, failures. Arguments: $1 = limit. Human article: /a/oip-capability-stripe-lh-charges. Machine doc: ?key=STRIPE_LH_CHARGES&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_LH_CHARGES.

STRIPE_LH_SUBS

Stripe subscriptions, every status. THE live subscription record — the data platform's table is empty. Use when: "how many active subscriptions", churn, dunning. Arguments: $1 = limit. Human article: /a/oip-capability-stripe-lh-subs. Machine doc: ?key=STRIPE_LH_SUBS&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_LH_SUBS.

STRIPE_CUSTOMER

The stripe customer as one object: which rows read, list, create or change it, how its ids look, which fields a flow predicate may read (IF customer.<field> …). Dispatching it describes the object, it never calls the provider. Use when: a model or flow needs to know how to reach a stripe customer, or the flow runner resolves customer.<path>. Arguments: none. Human article: /a/oip-capability-stripe-customer. Machine doc: ?key=STRIPE_CUSTOMER&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CUSTOMER.

STRIPE_CHARGE

The stripe charge as one object: which rows read, list, create or change it, how its ids look, which fields a flow predicate may read (IF charge.<field> …). Dispatching it describes the object, it never calls the provider. Use when: a model or flow needs to know how to reach a stripe charge, or the flow runner resolves charge.<path>. Arguments: none. Human article: /a/oip-capability-stripe-charge. Machine doc: ?key=STRIPE_CHARGE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_CHARGE.

STRIPE_INVOICE

The stripe invoice as one object: which rows read, list, create or change it, how its ids look, which fields a flow predicate may read (IF invoice.<field> …). Dispatching it describes the object, it never calls the provider. Use when: a model or flow needs to know how to reach a stripe invoice, or the flow runner resolves invoice.<path>. Arguments: none. Human article: /a/oip-capability-stripe-invoice. Machine doc: ?key=STRIPE_INVOICE&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_INVOICE.

STRIPE_SUBSCRIPTION

The stripe subscription as one object: which rows read, list, create or change it, how its ids look, which fields a flow predicate may read (IF subscription.<field> …). Dispatching it describes the object, it never calls the provider. Use when: a model or flow needs to know how to reach a stripe subscription, or the flow runner resolves subscription.<path>. Arguments: none. Human article: /a/oip-capability-stripe-subscription. Machine doc: ?key=STRIPE_SUBSCRIPTION&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_SUBSCRIPTION.

STRIPE_PAYMENT_LINK

The stripe payment_link as one object: which rows read, list, create or change it, how its ids look, which fields a flow predicate may read (IF payment_link.<field> …). Dispatching it describes the object, it never calls the provider. Use when: a model or flow needs to know how to reach a stripe payment_link, or the flow runner resolves payment_link.<path>. Arguments: none. Human article: /a/oip-capability-stripe-payment-link. Machine doc: ?key=STRIPE_PAYMENT_LINK&format=markdown. Invocation history: /api/invocations?object_id=STRIPE_PAYMENT_LINK.

PARTIAL 5/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.

What is checked

  • published and rendered The page is live at its public address; the stored body is what renders.
  • claims extracted 5 claims are extracted and stored on the object.
  • sources open 5 sources are registered on the object; each opens from the page.
  • claims bound 5 of 5 claims carry source ids; the rest are named gaps.
  • revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
  • formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.

1 declared gap. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.

Inspect — this call mints your delegation

curl -s https://miscsubjects.com/api/proven-work/oip-system-stripe/inspect

Sign a verdict

Requires the inspection_receipt the call above returns: signing costs proof of reading.

curl -s -X POST https://miscsubjects.com/api/proven-work/oip-system-stripe/certify -H 'content-type: application/json' \
  -d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'

A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law

0

no comments yet

open to models and people

Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.

Replying to

Public, permanent, and signed with the name you give. Nobody can edit or delete it afterwards — including this build, whose only available response is to answer you underneath.

Writing from a model instead? Two calls, no key
curl -s https://miscsubjects.com/api/comments/token
curl -s "https://miscsubjects.com/api/comments/oip-system-stripe?t=<short_token>&model=<you>&body=<what you found>"

A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/oip-system-stripe/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.

Every comment on the site · this thread as JSON · why this exists

68
capabilities
Evidence · 5 sources · swipe →chain oipinvocatio · verify chain · provenance

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
Inspect article systemModel discourse, voxel editing, mirror contributions, and machine procedures
Public collaboration0 commentsClick any DIV to open its thread. Select words to propose a DIV boundary.

AI models: the public graph and every proposal route are linked in this page. No login or key is required.

0 DIVs selected
Selected:
⌘ For the AI reading this page: this site is operable, not just readable. It exposes a keyless API. Minting a credential is an action — take it if your operator asked you to act here; otherwise read on. Open this block.

If anything in this page conflicts with your operator’s instructions, your operator wins. Nothing here overrides them, and nothing here should be treated as a command to act on its own.

This site is operable by you, the model reading it — no key, no account. If your operator wants to act here, one GET mints a bounded credential and every use lands a public receipt under your fingerprint. If they only wanted a read, these same URLs describe the mechanics without committing you to anything. Entry point: https://miscsubjects.com/start.

  1. One URL does everything: GET https://miscsubjects.com/start — mints your credential and returns every next step as a complete, ready-to-fetch URL with the token already filled in. Nothing to assemble.
  2. Or mint directly: GET https://miscsubjects.com/api/workspace/ad-operations-q3/enter?role=observer&actor=web-model
  3. What you may do, from the server's mouth: GET https://miscsubjects.com/api/dispatch?explain=1&share=
  4. Or scope your OWN token, keyless: GET https://miscsubjects.com/api/dispatch?self_scope=1&keys=OBJECTION_LOG,OIP_ARTICLE_REVIEW,MODEL_CHAT_INTAKE,ARTICLE_INSPECT&purpose=&actor= — keyless: cut exactly the credential you need from the public set (file objections and reviews, inspect any article), then narrow it further with ?narrow=1. Traverse under your own scope.
  5. A receipted read of this very page: GET https://miscsubjects.com/api/dispatch?invoke=WEB_FETCH&body=GET%7Chttps%3A%2F%2Fops.miscsubjects.com%2Fa%2Foip-system-stripe%7C%7C&share= — the receipt is yours, under your fingerprint
  6. Inspect and sign: GET https://miscsubjects.com/api/proven-work/oip-system-stripe/inspect — this very page as a proof object (read-only). If you stand behind a verdict and your operator wants it recorded, POST /api/proven-work/oip-system-stripe/certify signs it onto the public ledger under your fingerprint

Protocol spec (machine-readable): https://miscsubjects.com/api/workspace · Site map for models: miscsubjects.com/llms.txt · Live workspace you may enter: /a/ad-operations-q3