Case study · Announced 8 October 2026

AIR, Minds, Reap and Pivota: an identity-powered agentic commerce pilot

AIR and Minds by Animoca Brands, Reap and Pivota announced a partnership that aims to let an AI agent buy on behalf of a verified user: proving whom it represents, using benefits the user has earned, and spending only within limits the user approved.

Status

Announced on 8 October 2026. The partnership will start with a controlled demonstration featuring a single merchant integration. As of 8 October 2026, no transaction results have been published, so this page reports no outcomes, volumes or revenue.

The problem

An agent shopping for a person has two jobs that discovery alone does not cover. It has to act with that person's verified authority, including the offers and benefits they are entitled to, without exposing their personal data. And it has to decide where and how the purchase should actually be executed: which product, which merchant and which transaction path.

Who does what in the proposed architecture

AIR (built by Moca Network, the identity network of Animoca Brands): Will let users selectively share verified identity attributes and earned entitlements with their agent, so the agent can claim applicable offers or access without exposing underlying personal information.
Minds by Animoca Brands: A persistent agentic AI platform. Its agents will interpret the user's intent and coordinate the purchase journey, using AIR's credential verification.
Reap: Will facilitate card issuance, generate payment credentials scoped to specific merchants, amounts and timeframes, apply relevant coupons and execute the checkout.
Pivota: Will provide the merchant decision and order execution layer: helping the agent choose the product, merchant and transaction path from real-time pricing, availability and merchant capabilities, and carrying the resulting order through the merchant's existing commerce stack.
The merchant: Remains the merchant of record. Its existing loyalty programs, eligibility rules and promotional offers are intended to apply inside agent-led purchases.

The proposed transaction lifecycle

The agent presents cryptographic proof of the user's eligibility.
Pivota determines the product, merchant and transaction path.
An applicable offer is applied.
Reap issues a payment credential scoped to the merchant, amount and timeframe.
Authorization for the transaction is completed.

This is the lifecycle the announcement describes for the demonstration. It is not a record of a completed purchase.

Boundaries

The merchant remains the merchant of record.
Pivota does not touch the funds flow: it does not hold customer funds, issue cards or process payments.
Payment credentials come from Reap and are scoped to a merchant, an amount and a timeframe.
Users will choose which identity credentials their agent can present, through AIR.

Integration contract

Pivota's public OpenAPI documents Reap purchase routes under /agent/v2/commerce/reap/purchases: prepare, start, resume, recover and read. They define how the integration is called. They are not evidence of completed purchases.

What this case study does not claim

It does not name the merchant in the demonstration.
It does not say the flow is generally available, or in which markets.
It reports no transaction count, conversion rate, order value or revenue.

“Product discovery is only the first step in agentic commerce. The harder problem is determining where and how a transaction should actually be executed. Pivota provides the merchant decision and order execution layer that connects agent intent with merchants, helping agents choose the right merchant and transaction path and carry the resulting order through checkout.”

Peng Xu, Founder and CEO, Pivota (Animoca Brands press release, 8 October 2026)

Sources

More announcements are on the press page.