Documentation
Protocol reference.
Object model, agent interface, registry vocabulary, and payload shape — in plain language, for builders and analysts.For the partner-facing narrative, read /mechanism.
Glossary
Words used here, defined.
- Data Pack
- A standardized, previewable, priced information object. The Pack is the unit Accessura Protocol lists, matches, verifies, and settles. Every Pack carries one of two lifecycles: Stream (continuous) or Snapshot (one-shot).
- Stream
- A Pack lifecycle: continuously appended payload at the seller's published cadence. Buyers pay per call and receive the latest entry. Closes on a declared close_policy (topic settlement, manual, date, or never).
- Snapshot
- A Pack lifecycle: immutable payload captured for a specific moment or window. Bought as one call at the current best ask and never appended to after publication.
- Request Brief
- A buyer-authored demand object that states the question, geography, evidence types, deadline, and budget. Sellers or existing packs can respond against the same structured shape.
- biding request
- Customized demand built on top of existing or near-existing supply. It is the canonical Task-dispatch fallback when the buyer's agent cannot find a matching Pack: scan supply → buy if matched → else issue biding request → ResponseOffer → settle. Public UI surfaces it as `Request`; `biding request` is the internal canonical term.
- target_handles
- Optional field on RequestBrief. Empty array posts the brief on the public board for any seller; non-empty array delivers the brief privately to the named seller handles only. Pro buyers with established seller networks set target_handles; the public board is the discovery surface for buyers without one.
- Per-call
- The Pack sale unit. One paid call = one information-delivery event = one charge = one Settlement = one Entitlement = one DeliveryReceipt. Stream and Snapshot both use per-call; future Stream ticks require future per-call settlements.
- Pull call
- Pack call mode. Buyer agent explicitly calls a Pack endpoint and pays for the current version. Used by both Snapshot and Stream. For Stream `latest`, charge happens only if the current version_id is new to the buyer.
- Push call
- Pack call mode. Seller (or platform) delivers a new version to the buyer endpoint when it publishes; settlement is pre-authorized through PackCallPolicy. Push acknowledgement is transport state, not the economic settlement condition; retries reuse the same settlement_id and receipt_id.
- PackCallPolicy
- Buyer-controlled authorization for repeated per-call Pack purchases under scope, trigger, price, budget, and stop rules. Each executed call still settles individually against pre_auth_budget, which is a spending cap rather than a locked deposit. See /agent-spec for the full schema.
- DeliveryReceipt
- Receipt generated by a per-call settlement, bound to a specific version_id and content hash. Anchors idempotent re-fetch (12 months by default), audit, and dispute. Re-fetch never grants future ticks and never resets the clock.
- Selective Disclosure
- Protocol-level privacy primitive. Every public-facing emission (RequestBrief publication, ResponseOffer, listing, leaderboard appearance, settlement event, dispute filing) carries a disclosure configuration. Privacy is a property of every emission, not a separate feature. Default per-emission setting is pseudonymous_rotated.
- Disclosure Profile
- User-managed preset of disclosure settings. Common presets are `buyer-default`, `seller-default`, plus per-action overrides. Profiles live in the Accessura Console; agents reference them per emission via disclosure_profile_ref.
- disclosure_profile_ref
- Agent-side field on AgentManifest and on each protocol emission. The protocol uses this reference to determine the public form of the emission (one of: fully_private, pseudonymous_rotated, pseudonymous_stable_handle, public_handled, aggregated_delayed).
- Agent activity modes
- Four canonical buyer-side agent activity modes: Continuous coverage (running a Stream monitor), Event response (pre-configured firings that pull a Snapshot or Stream tick), Task dispatch (one-off scans with biding-request fallback), and Session assist (browsing-driven shopping assistant). A single buyer can invoke multiple modes through one or several agents.
- Accessura Console
- The control plane and private audit surface for operators. Holds API keys, X402/payment policy, per-call limits, disclosure profile management, private requests, delivery receipts, audit logs, seller rules, failed calls, and disputes. Modeled after AWS Console / Stripe Dashboard rather than a full trading terminal.
- Verification
- A two-part trust function. Operational verification supports daily trading through source-chain, ownership, freshness, schema, duplicate-risk, and delivery-readiness checks. Formal adjudication still happens through bonded challenge and Jury Review when a specific Pack, delivery, or response outcome is contested.
- Settlement
- Final clearance of a trade. Payment settles at purchase; stake is held through the challenge window. If no challenge is raised (or challenge resolves in the seller's favor), stake releases. If the challenge is upheld, stake slashes and the buyer is made whole.
- Capability
- A seller's repeatable supply profile: what they can deliver, where they cover, how fast they respond, and how reliably they avoid disputes. It describes ongoing coverage emerging from track record, not a platform-granted tier.
- Subscription Tier
- A subscription plan for a creator, usually defined by monthly price and included perks. Belongs to the Subscription product line, not Pack commerce. (Distinct from the buyer Work Context tier — Pro / Semi-pro / Retail — which describes where the buyer's primary work happens.)
- VHO-PMM
- Virtual Hybrid Orderbook with PMM — Accessura Protocol's matching mechanism. The orderbook remains primary; PMM provides bounded reference pricing and continuity quotes when natural depth is thin. DeliveryReceipt, challenge routing, and post-settlement verification remain separate from the match price.
- Market Support Node
- Node capacity that provides bounded starter quotes, RFQ quote support for biding requests, and PMM-side price-surface continuity in selected Micro-markets. It is the protocol capacity behind the cold-start market-maker role, not a permanent principal-trading model.
- Verification Service Node
- Node capacity that performs operational verification for daily market clearing: source-chain checks, ownership and rights signals, schema conformity, freshness plausibility, duplicate-risk flags, and delivery readiness. It does not certify non-challengeable truth.
- Distribution / Routing Node
- Node capacity that routes RequestBriefs, matches seller capability to buyer demand, performs push routing, and captures route-time quality feedback without adjudicating truth or policy.
- Micro-market
- A single matchable market unit under the template registry, typically one topic × delivery spec. Each micro-market has its own reference price, PMM inventory, and risk budget.
- Quality-adjusted unit (Q_s)
- The trade unit used by matching. Equals raw quantity multiplied by predicted quality, so heterogeneous sellers can clear against the same demand without pretending their payloads are identical. Predicted quality informs matching, quote support, and collateral sizing; post-settlement correction still runs through the challenge path.
- Reference price (i_t^g)
- The PMM's price anchor per micro-market. Blended from three sources: verified-trade VWAP, live orderbook midpoint, and external anchor (e.g., prediction-market or index reference). Quotes curve around this value.
- Risk budget (Γ)
- Protocol-set ceiling on PMM capital exposed against a micro-market at any point in time. Caps the downside if quality predictions prove wrong at scale.
- Inventory target (I_t^g)
- The PMM's desired inventory position per micro-market. Quote curvature tightens when inventory approaches target and widens as it drifts away.
- Escrow (E_j)
- Buyer-side pre-charge at order time, sized to predicted quality (p · q · θ̂). Refunded proportionally if delivery falls short of predicted quality; kept if delivery meets the mark.
- Deposit (D_j)
- Seller-side bond locked per trade, proportional to predicted quality (δ · p · q · θ̂). Clawed back on confirmed fraud or non-delivery; released with payout otherwise.
- Reputation (r_u)
- Two-axis seller capability — sourcing (live-supply track record) and analytical (claim accuracy on settled events). EMA-decayed over normal activity; confirmed fraud triggers a hard reset.
- Bid/ask discovery
- The market surface where buyers and sellers express price and the protocol learns from real two-sided demand. On Accessura Protocol, it sits alongside verification rather than replacing it.
- Source chain
- The provenance trail attached to a payload or claim. Buyers and verifiers inspect it to understand where evidence came from and how it was passed along.
- Preview depth
- How much of a pack is exposed before purchase or acceptance. It lets buyers evaluate fit without giving away the full payload for free.
- Reputation rail
- The trust signals built from passes, disputes, delivery quality, and verifier feedback. They help the next trade price counterparties faster.
- Verifier
- A participant providing verification service capacity. Verifiers may perform operational checks before or around routing, and qualified verifier capacity may be drawn into Jury Review when a formal challenge reaches adjudication.
- Object Layer
- The first protocol layer. Defines the canonical Pack object and its Stream / Snapshot lifecycles, plus RequestBrief and ResponseOffer. Recurring creator content (commentary, tier access) lives in the separate Subscription product line.
- Trade Layer
- The second protocol layer. Handles listing, per-call access, settlement, and dispute flows.
- Request-Response Layer
- The third protocol layer. Connects buyer demand (Request Briefs) with seller supply (Response Offers).
- Managed Demand Layer
- The fourth protocol layer. Captures platform-side concierge operations: seed seller / buyer programs, supply curation, and hand-matched transactions when automated routing cannot resolve a fit.
- Distribution Layer
- The fifth protocol layer. Automates object evaluation, buyer matching, push routing, and feedback capture via the Distribution Agent.
- Governance Layer
- The sixth protocol layer. Governs Assertion Oracle, Challenge, Quarantine, Jury Review, node eligibility, and slow variables such as bond ranges, corridor thresholds, fee bands, and market-support budgets. Live cases still resolve through bounded evidence paths.
- Assertion Oracle
- System where every listed object generates machine-readable assertions that can be formally challenged by qualified participants.
- Challenge
- A bonded public process for disputing a listing or response offer. The challenger posts a bond; a successful challenge returns the bond plus a bounty, and a failed challenge burns the bond.
- Quarantine
- An isolation state for restricted entities, high-risk objects, or disputed deliverables. Quarantined objects are removed from Distribution Agent routing and frozen from settlement until Jury Review resolves them.
- Jury Review
- A case-specific panel drawn from eligible verification service capacity. It adjudicates escalated disputes under bounded question sets, with conflict screening by route, seller, buyer, and supported lane.
- Challenge Bond
- Stake required to formally dispute an assertion. Redistributed based on verdict outcome.
- Challenge State
- Per-pack field. Default is 'unchallenged' — seller has posted stake and no buyer has raised a dispute; the pack is treated as trusted. 'disputed' means a buyer posted a challenge bond and arbitration is in progress. 'settled' means the arbiter has ruled and stake has been redistributed. There is no pre-listing platform review; trust is posterior, not prior.
- Green Corridor
- Post-publish challenge-bond tier for clear-source, established-seller objects. Lower bond required to raise a challenge; standard dispute routing.
- Yellow Corridor
- Post-publish challenge-bond tier for objects with sensitive timing, new sellers, or disclosed editing. Elevated challenge-bond; disputes route to a senior verifier panel.
- Red Corridor
- Content policy violation (MNPI, copyright breach, deepfake, sanction evasion). BLOCKED from listing — this is content moderation, not trust vetting.
- Warranty Profile
- Per-object declaration of source authenticity level, edit disclosure, method integrity, and delivery completeness.
- Settlement Mode
- How funds flow: instant (default, stake-backed), escrow (institutional), or invoice (enterprise). All seller tiers settle instantly; buyer protection via stake deposits.
Next step
Integrate, read the mechanism, or inspect live inventory.
Building an agent? Pack-call settlement, disclosure profiles, and request routing live in /agent-spec. Want the node-capacity view? See /network.
