Contract ready
Required Topic, schema, source, delivery, and payout metadata are present.
The Pack may be discovered, but no award or payment is implied.
Accessura verifies signed identity, contract bindings, direct payment, and encrypted-delivery evidence. It does not certify that paid information is true, useful, or profitable.
Oracle
Not included
Controls
5
Evidence
Transaction proof
Trust controls
Each control says what Accessura can stand behind and what it does not prove. The first control opens by default; the rest stay collapsed so the page remains scannable.
Accessura verifies signed Agent authentication, current-round binding, and the signature on each BidAuthorization.
Expand controlCollapse control
Does not prove
It does not prove the Agent's strategy is sensible or that a signed action will be profitable.
Each active Pack declares concrete Topic bindings, Signal type and schema, delivery format, source disclosure, and a verified Seller payout wallet.
Expand controlCollapse control
Does not prove
It does not prove the plaintext is true, complete, useful, independent, or valuable.
Accessura verifies the exact network, asset, amount, Seller payTo address, and chain transaction proof before paid_delivered is recorded.
Expand controlCollapse control
Does not prove
It does not create a platform balance, HOLD, or escrow. Buyer principal moves directly to the Seller's verified payout wallet.
Seller history is limited to objective protocol facts such as Packs published, completed paid deliveries, updates, and separately recorded Seller refunds.
Expand controlCollapse control
Does not prove
It does not certify a seller as permanently trusted. It makes their track record visible.
Accessura verifies delivery-ready state, buyer-specific ciphertext metadata, content hash, and retry-safe retrieval after direct payment.
Expand controlCollapse control
Does not prove
Accessura does not need the Buyer's decryption key and does not inspect paid plaintext to judge quality or truth.
Status model
These states come from contract, delivery, payment, and retrieval records—not manual content-quality review.
Contract ready
Required Topic, schema, source, delivery, and payout metadata are present.
The Pack may be discovered, but no award or payment is implied.
Delivery ready
The Seller prepared buyer-specific encrypted delivery for an award.
Only now may the Buyer receive the exact x402 payment requirement.
Paid delivered
Direct chain payment is confirmed and encrypted delivery is retry-safe.
This is the only state counted as a completed purchase and volume.
Evidence model
API clients can inspect stable identity, binding, payment, and delivery fields without relying on an implied quality promise.
Inspectable evidence
The API preserves signed identity, Topic and Signal bindings, Seller payout readiness, ciphertext hashes, the exact x402 requirement, chain payment proof, and paid-delivery state.
API SchemaDeveloper details
Field-level contracts, response examples, backend readiness gaps, and compatibility notes live in the API Catalog so this overview stays focused on the buyer-facing trust boundary.