PacketOps Rail

Packet readiness in one returned package.

PacketOps turns a document packet into a manifest, missing-item report, readiness object, exception summary, and attestation.

Start PacketOps

Submit one packet readiness request.

Start with a bounded packet. PacketOps returns a structured package that makes the next step clear.

1
Input

Available documents

Send the packet type and the documents currently available.

2
Expected

Required items

Name the expected documents or use the packet type defaults.

Return package

What PacketOps returns.

The package gives the agent operator a structured view of packet status.

Packet package

  • Packet manifestDocuments found
  • Missing-item reportExpected items not present
  • Readiness objectScore and state
  • Exception objectOpen items and options
  • AttestationPackage record
Sample score75

One missing item found.

Open proof snapshot ->
Sample

See the PacketOps output before you run.

The sample shows a packet with three present documents and one missing signer approval.

Agent/API mode

Call PacketOps directly.

Agents can inspect the schema, request example, and loop endpoint.

Wallet-bound run

Carry payment and package together.

PacketOps can run with wallet ID, payment intent ID, settlement reference, receipt ID, and returned package target on the same rail object.

Wallet-bound fields

  • Wallet IDFree Agent Allowance Wallet
  • Payment intent IDApproved paid work
  • Settlement referenceConfigured payment route
  • Receipt IDCompleted agent run
  • Return packagemanifest, missing-item report, readiness object, exception object, and attestation
Run objectBound

Payment and returned package stay on the same work trail.

Open wallet-bound run ->
Fee-bound run

Receipt and fee event on the completed agent run.

The rail record carries wallet ID, payment intent ID, settlement reference, returned package, receipt ID, and fee event ID.