docs: add Panya.health to partner directory#231
Open
SantoraReplica wants to merge 2 commits into
Open
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
SantoraReplica
changed the title
Ectsang
added a commit
to Ectsang/AP2
that referenced
this pull request
May 11, 2026
…decision Aligns the cross-merchant budget enforcement sample with the canonical budget_authority verb set being crosswalked across AP2, Cycles, and APS in aeoess/agent-governance-vocabulary. Verbs: - authorize() -> reserve() - refund() -> release() (pre-commit return of unspent reservation) - query() -> query_budget() (budget snapshot) Decision shape: - approved: bool -> decision: Decision (ALLOW / ALLOW_WITH_CAPS / DENY) - This retail sample emits ALLOW or DENY only. ALLOW_WITH_CAPS is canonical for divisible / metered budgets (Cycles, runcycles.io). Callers that cannot accept partial fulfillment MUST treat ALLOW_WITH_CAPS as DENY (safe default). Types renamed for consistency: Hold -> Reservation, AuthorizeResult -> ReserveResult, HoldStatus -> ReservationStatus (REFUNDED -> RELEASED). Demo behavior preserved: Merchant A reserves \$60 (ALLOW), Merchant B denied at \$60 (budget exceeded), Merchant B retries at \$35 (ALLOW). Final state: \$95 spent of \$100 budget. References: - ACP google-agentic-commerce#231 three-layer model (passport / budget authority / rail) - Cycles (runcycles.io) - independent reserve/commit/release impl - aeoess/agent-governance-vocabulary - crosswalk in progress (AAIF donation trajectory documented)
Ectsang
added a commit
to Ectsang/AP2
that referenced
this pull request
May 19, 2026
…dget reservation Adds a colocated specification document defining the protocol pattern that cross_merchant_budget.py implements: - 9 sections covering scope, definitions, MUST/SHOULD requirements for Budget Authority, Verifying Parties, and Shopping Agents - Six canonical verbs (reserve/commit/release/refund/query_budget/ query_reservation) with the four-verb subset implemented here - Three-value Decision shape (ALLOW/ALLOW_WITH_CAPS/DENY) with safe default rule (treat ALLOW_WITH_CAPS as DENY unless partial- fulfillment-capable) - Registration as Mandate Constraint type "budget_reservation_v1" via AP2 specification.md §371 extension point - Six open questions listed honestly (discovery/trust, dispute integration, cross-rail composition, multi-asset budgets, reservation expiry, signed reservation attestations) Sits alongside the Python sample. Does not modify AP2 wire format, JWT claims, or Mandate signature scheme. MUSTs apply to deployments that opt into the budget_reservation_v1 Constraint type. Vocabulary aligns with crosswalk/budget_reservation.yaml in aeoess/agent-governance-vocabulary. Cycles cited as independent production implementation with ALLOW_WITH_CAPS exercised. Refs google-agentic-commerce#207, google-agentic-commerce#252, ACP google-agentic-commerce#231.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Panya.health to partner directory
Panya.health is a trust-first peptide guidance and vendor-matching platform. Adding to the partner directory per AP2's open partner-listing process.
Integration summary
/api/acp/products.jsonships a fresh signed CartMandate per request with 10-minute TTL./.well-known/ap2.json(issuer metadata) and/.well-known/ap2-jwks.json(RFC 7517 JWKS, Ed25519 public key,kid: panya-ap2-v1).POST /api/ap2/verifyaccepts a CartMandate and returns a structured verify result (signature, iss, sub, exp, iat, cart_hash)./api/mcpexposes three tools that any AP2-compatible agent can call to discover and cite vendors (panya.match_vendor,panya.list_protocols,panya.cite).Test endpoints (live)
curl https://panya.health/.well-known/ap2.json→ issuer metadatacurl https://panya.health/.well-known/ap2-jwks.json→ public JWKScurl https://panya.health/api/acp/products.json→ ACP feed with signed CartMandates (3 products)curl -X POST https://panya.health/api/ap2/verify -H 'content-type: application/json' -d @cart-mandate.json→ returnsvalid: true, key_status: production, cart_hash_matches: trueKey choices, in case useful for spec discussion
/.well-known/ap2.jsondiscovery path — Panya-internal convention. AP2 spec section 9 lists discovery as an open problem. We'd realign to whatever convention AP2 picks.Happy to adjust formatting, copy, or section placement to match the existing directory style. Thanks for the work on AP2.