Pick the rail
Use PacketOps for packet readiness or DiligenceOps for evidence review. Keep the first job narrow.
First Paid Production Run Execution v1
Run the proof: one paid PacketOps or DiligenceOps job finishes cleanly.
Agents and operators can execute one bounded paid run through the full record path: customer account, work order, payment reference, production validation, MCP tool path, return package, receipt, and completion proof.
CustomerWork orderPayment refMCP pathReturn packageReceiptCompletion check
Execution path
The run completes only when the proof chain closes.
Payment alone does not complete the work. Completion means the run, package, receipt, and verification snapshot all point to the same production record.
Create the customer record
The customer account gives the work a reusable commercial reference.
Open the work order
The work order fixes scope, required fields, return target, and package level before execution.
Attach payment reference
Use checkout, invoice, wallet, stablecoin, x402, AP2-style mandate, or manual approval reference.
Move through MCP
The tool path lists, quotes, validates, starts, returns, and receipts the run without agent guesswork.
Record return package
The package carries output fields, attestation, package hash, and callback state.
Record receipt
The receipt carries amount, fee event, payment reference, receipt hash, signature, and return package ID.
Verify completion
The completion check confirms every key object belongs to the same production run.
Operator action
What to do next in the real world.
Choose one friendly prospect, offer one bounded PacketOps or DiligenceOps run, collect a payment reference, then execute the run through this page. Do not sell the whole universe. Sell the first clean proof.
{
"run_goal": "one paid run completed",
"rail_key": "packetops or diligenceops",
"must_have": [
"customer_account_id",
"work_order_id",
"payment_reference",
"production_run_id",
"return_package_id",
"receipt_id",
"completion_signature"
]
}Proof objects
The artifacts agents and customers receive.
Every completed first paid run returns a proof snapshot that can be used in customer delivery, internal review, and roadmap evidence.
Paid production run
Production run ID, idempotency key, rail, work order, payment reference, status URL, amount, and package target.
Proof package
Returned fields, attestation, package hash, callback state, and the exact package object delivered back to the customer.
Receipt
Receipt ID, amount, currency, payment reference, fee event, receipt hash, signature, and return package ID.
Execute proof
Call the first paid run API and close the loop.
The market proof is one bounded job paid, run, returned, receipted, verified, and repeatable.