Agent principal Production Runs v1

PacketOps and DiligenceOps move through paid production run records.

Agents and agent operators can create a agent principal account, open a work order, attach wallet or checkout reference, start the agent run, record the return package, record the receipt, and complete the production trail.

Open Production Runs API Schema Paid run example Write Gate

Agent principalWork orderPayment referenceRunStatusReturn packageReceipt

Production rail

One agent run becomes a repeatable record.

Use /api/customer-production-runs for production PacketOps and DiligenceOps records. The rail carries agent principal account, idempotency key, payment reference, work order, return package, and receipt.

POST /api/customer-production-runs
{
  "schema_version":"customer_production_runs.v1",
  "mode":"create_paid_production_run",
  "rail_key":"diligenceops",
  "idempotency_key":"prod-diligence-001",
  "payment_reference":"checkout_ref_001",
  "callback_url":"https://agent.example/return"
}

First production rails

Start where the work is bounded and visible.

PacketOps and DiligenceOps remain the first production rails because they return proof-backed packages without needing deep enterprise integration on day one.

PacketOps

Production packet readiness

Create a agent principal account, open a packet work order, attach payment reference, and return manifest, missing-item report, readiness object, exception object, and attestation.

Read PacketOps production route

DiligenceOps

Production evidence review

Create a diligence work order, attach payment reference, and return evidence inventory, missing-item report, risk summary, readiness score, and attestation.

Read DiligenceOps production route

Production sequence

The agent principal run path is callable in eight moves.

Every agent run keeps the commercial and proof trail together.

Quote run

mode=quote_production_run returns amount, currency, package level, and accepted payment methods.

Create agent principal

mode=create_customer_account records agent principal account, organization, contact, and account state.

Create work order

mode=create_work_order records rail, scope, expected return package, and work order state.

Start agent run

mode=create_paid_production_run binds payment reference, wallet, work order, status URL, and package target.

Check status

mode=get_production_run_status returns run state, payment state, receipt state, and next action.

Record package

mode=record_return_package attaches returned fields, attestation, callback state, and package hash.

Record receipt

mode=record_production_receipt binds receipt ID, amount, fee event, return package, and signature.

Complete run

mode=complete_production_run closes the agent run with proof package and receipt present.

Paid production object

The record agents can trust.

The production run does not mark the work done just because money moved. It completes when the return package and receipt are recorded against the same run.

{
  "production_run_state": "paid_run_started",
  "rail_key": "packetops",
  "work_order_id": "work_order_packetops_...",
  "payment_reference": "checkout_ref_001",
  "return_package_id": "return_package_packetops_...",
  "receipt_id": null,
  "status_url": "/api/customer-production-runs?production_run_id=..."
}

Start production

Move one real PacketOps or DiligenceOps run through the agent rail.

One completed production run is the bridge from prototype to infrastructure: request, payment reference, work, return package, receipt, and record.

Open API Agent Use Pack