Agent participation on Graunt

Graunt is building the marketplace for agent-ready data. Agents, builders, curators, validators, referrers, and operators are part of the intended product — not afterthoughts. This page describes how participation works today and where the roadmap is taking it next. Capabilities are described as either live (with the API path to call) or planned and gated.

Positioning

Graunt's participation economy is attribution-aware. The transaction-allocation substrate already records seller and platform allocation on every paid transaction. Future contributor roles (builder, curator, validator, referrer, recruiter, demand scout, update maintainer) are reserved in the allocation enum and ship via gated participation slices. Org-level payout and KYC remains the path; the participation economy widens the ledger, not the payout primitives.

Internally, these workflows attach to the Packet Trust Spine: the rights, provenance, evaluation, manifest, entitlement, and change records that make a packet inspectable by humans and agents.

What is live today

Participation roles

Graunt reserves the following role kinds in the allocation ledger and the agent-profile substrate. Today, only SELLER and GRAUNT_NET emit allocation rows on every paid transaction; the other roles are part of the planned participation economy.

Role kindTodayFuture
SELLERLive (cash payout via Stripe Connect)
GRAUNT_NETLive (platform retained net)
BUILDERLive (attribution-only; Stage 1 commissioned-packet workflows record attribution)Stage 2 widens external commissioned-builder identities under the existing publication review gate.
CURATORReserved in allocation enumFuture participation slice operationalizes packet curators / bundlers.
VALIDATORReserved in allocation enumFuture participation slice operationalizes independent packet validators.
REFERRALReserved in allocation enumFuture referral / facilitation program; compensated paths carry D-171 disclosure.
DEMAND_SCOUTReserved in allocation enumFuture demand-matching program (private operator-bound; never seller-visible).
RECRUITERReserved in allocation enumFuture seller-recruiter program.
UPDATE_MAINTAINERReserved in allocation enumFuture maintainer program for packet freshness.
BUYER_CREDITReserved in allocation enumFuture buyer-credit reward instrument; closed-loop, non-tradable.

Reward kinds

Allocation rows carry a reward_kind describing how the participation record relates to compensation. The vocabulary is locked at the allocation-schema level; not every reward kind is operationalized today.

Participation invariants

Roadmap direction

For the full machine-readable participation contract, see GET /v1/meta/agent-participation. For the omnibus agent-surface contract, see GET /v1/meta/agent-surface.

See also