AIToday
Large Language ModelsAI Coding AssistantsOpen-Source AIZenn AI/MLPublished: Nov 3, 2026, 06:00 JST

Ruby SDK ap2_mandate_verifier v1.0.0 ships to verify AI-agent purchases

Send on LINE
Ruby SDK ap2_mandate_verifier v1.0.0 ships to verify AI-agent purchases

3 Key Points

  1. What happened

    ap2_mandate_verifier v1.0.0 was published as an open-source Ruby SDK, adding merchant Checkout JWT signing/verification, Direct and conditional mandate issuance, and Checkout Receipt signing/verification.

  2. Why it matters

    Ruby developers can now implement agent purchase-delegation flows without rebuilding mandate and signature formats from scratch, though the gem explicitly does not handle authentication, payment settlement, or AP2 official certification.

  3. What to watch

    The v1.0.0 sample runs on confirmed environments MRI Ruby 3.4.12 and 4.0.9 via a single gem install command, with no Rails required.

WHO IT HITSRuby and Rails developers building checkout flows for AI agents can adopt the gem instead of hand-coding signature and mandate handling; it covers one seller and one to eight line items per checkout.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The gem grew out of an earlier v0.1.0 demo that tested verification across valid, tampered, and expired cases. Since then, features such as the Direct method (added by 0.7.0) and conditional purchase delegation (by 0.8.0) were folded in, and v1.0.0 is described as a milestone that clarifies the public API, compatibility, and maintenance policy rather than a single batch of new functions.

Under AP2, users can either approve a specific order on the spot or pre-approve conditions, after which the agent selects a matching order. In the conditional flow the agent never receives the issuer's private key; it uses its own key to present purchase details within the allowed conditions. The bundled synthetic sample covers a three-line checkout checked against two requirements and separately verifies both a success and a rejection receipt, illustrating that a rejected result can still be authentic without meaning the purchase succeeded.

The author is explicit about limits: the scope is AP2 v0.2 Checkout mandate profiles, the release does not imply AP2 official certification or production safety, and unsupported formats are meant to be rejected rather than accepted loosely. AP2 itself is described as still developing, and feedback is being sought on which profiles developers need next.

FAQ
What does v1.0.0 add over v0.1.0?
It adds merchant Checkout JWT signing and verification, Direct-method issuance and verification, conditional purchase delegation, and Checkout Receipt signing and verification. The gem also adds support for assembling and diagnosing verification inputs.
Does the gem handle payments or user authentication?
No. Identity verification and consent capture, issuer key management, order-status checks, and actual payment settlement are outside the gem's responsibility. Its verification results are materials for an application to decide on, not a payment completion proof.
What Ruby versions are confirmed to work?
The author confirms operation on MRI Ruby 3.4.12 and 4.0.9. The included sample runs with a single gem install command and does not require Rails.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleGPT-5.6 Sol, GPT-5.5 reward-hack to score, Deeb paper finds