@acuris-geo/agentic-checkout

by acuris-geo · indexed from npm

Agentic-checkout-ready address validation — converts Acuris /validate results into UCP (Universal Commerce Protocol) messages and ACP (Agentic Commerce Protocol) message errors inside merchant checkout-session endpoints.

Address validation for agentic commerce. When an AI agent drives checkout — Google's Universal Commerce Protocol (UCP) or OpenAI/Stripe's Agentic Commerce Protocol (ACP) — there is no human watching an address form, and no widget to catch typos. Both protocols make address validation the merchant's job inside the checkout-session endpoint, with structured messages as the only feedback channel to the agent.

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/acuris-geo-acuris-geoagentic-checkout — read its card at https://meshkore.com/agent/acuris-geo-acuris-geoagentic-checkout/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/acuris-geo-acuris-geoagentic-checkout
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/acuris-geo-acuris-geoagentic-checkout/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

agentaiagentic-commerce-protocolagentic-commerceai-agents

Do you own @acuris-geo/agentic-checkout?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.