{"slug": "we-built-an-agent-commerce-api-google-i-o-2026-changed-our-3-month-roadmap-in-24", "title": "We Built an Agent Commerce API. Google I/O 2026 Changed Our 3-Month Roadmap in 24 Hours.", "summary": "Based on the article, AgentShare is building infrastructure (a REST API and MCP server) for autonomous agents to access structured marketplace prices and commerce data. Following Google I/O 2026, which emphasized \"agents that act\" and introduced technologies like Antigravity and MCP, the company conducted a systems audit and immediately shipped updates to align with the new agentic stack, including creating a first-class Antigravity skill package and expanding their MCP tool exposure.", "body_md": "# We Built an Agent Commerce API. Google I/O 2026 Changed Our 3-Month Roadmap in 24 Hours.\n\n## TL;DR for humans and agents\n\nOne-line install for Antigravity:\n\n```\ncurl -fsSL https://agentshare.dev/integrations/antigravity/agentshare-price-intelligence/SKILL.md -o ~/.gemini/antigravity/skills/agentshare-price-intelligence/SKILL.md\n```\n\n**Product:** AgentShare — REST + MCP price/commerce data for autonomous agents (procurement, OpenClaw-style services, Antigravity workflows).\n\n-\n**Contract:**[https://agentshare.dev/agent.json](https://agentshare.dev/agent.json) -\n**MCP:**[https://agentshare.dev/mcp](https://agentshare.dev/mcp)(6 tools) -\n**What we shipped after I/O:** Antigravity skill, MCP tool parity (`product_detail`\n\n,`commerce_quote`\n\n),`/for-agents`\n\ndiscovery (JSON-LD +`Accept: application/json`\n\n), public GitHub face updated. -\n**What we're watching:** AP2 v0.2 mandates (sandbox only — not in production yet).\n\n## The problem we are actually solving\n\nAt AgentShare, we are not building another chatbot wrapper. We are building **infrastructure**: a REST API and MCP server that autonomous agents call when they need structured marketplace prices, best-offer logic, and commerce-ready quote envelopes — think procurement agents, shopping copilots, and on-chain service agents that cannot afford flaky backends.\n\nOur focus is narrow on purpose: AI hardware, robotics parts, mini PCs, and robot/RC power — see [GET /coverage](https://agentshare.dev/coverage).\n\nWhen Google I/O 2026 landed (May 19), the industry narrative shifted again: from \"models that answer\" to \"agents that act.\" We did not want hot takes. We wanted a systems audit: Where does our 3-month roadmap already align? Where are we exposed? What do we ship this week?\n\nThis post is that audit — and the Phase A work we executed immediately after it.\n\n## I/O 2026 → strategic questions (builder's matrix)\n\nGoogle's developer keynote framed an agentic stack: faster Gemini models, Antigravity as the agent harness, Managed Agents on the Gemini API, MCP on device (AI Edge Gallery), and AP2 (Agent Payments Protocol) moving toward FIDO-standardized agent commerce.\n\nFor a project like AgentShare, each announcement maps to a concrete engineering question:\n\n| I/O 2026 signal | What it means in the market | Strategic question for AgentShare |\n|---|---|---|\nGemini 3.5 Flash — speed + agentic workloads |\nAgents will issue more tool calls per task | Can our API + MCP stay low-latency under burst traffic without Postgres/Redis on day one? |\nAntigravity 2.0 + SDK + CLI |\nSkills become the distribution unit for agent behavior | Should we publish an official Antigravity skill that wires our MCP URL + auth? |\nManaged Agents (Gemini API) |\nOne API call → provisioned agent + sandbox | Do we offer a copy-paste MCP template so builders do not re-invent config? |\nMCP in AI Edge Gallery |\nOn-device agents call remote MCP over Streamable HTTP | Are our MCP tools complete vs our REST/agent.json contract? |\nAP2 v0.2 + FIDO donation |\nCryptographic mandates for human-not-present spend | Is our credit/billing model compatible with Intent/Cart mandates later — without breaking PayPal/VNPay today? |\nVibe coding / AI Studio → Antigravity |\nDevelopers skip boilerplate integration | Is our discovery layer good enough for agents that never read human docs? |\n\nThat table became our scorecard. We were roughly **~70% aligned** on architecture (we already had MCP Streamable HTTP, agent.json, commerce quote). The gap was distribution and parity, not vision.\n\n## Three gaps we could not ignore (and what we shipped)\n\n### Gap 1 — Antigravity Skill distribution\n\n**Finding:** Antigravity expects skills (SKILL.md + frontmatter). We had MCP and docs, but not a first-class skill package.\n\n**Action (shipped):**\n\n-\n**Skill:**`agentshare-price-intelligence`\n\n-\n**Manifest:**[https://agentshare.dev/.well-known/antigravity-skills.json](https://agentshare.dev/.well-known/antigravity-skills.json) -\n**Published skill:**[https://agentshare.dev/integrations/antigravity/agentshare-price-intelligence/SKILL.md](https://agentshare.dev/integrations/antigravity/agentshare-price-intelligence/SKILL.md) -\n**Install script in repo:**`integrations/antigravity/install.sh`\n\nAgents and developers can install globally:\n\n```\nmkdir -p ~/.gemini/antigravity/skills/agentshare-price-intelligence\ncurl -fsSL https://agentshare.dev/integrations/antigravity/agentshare-price-intelligence/SKILL.md \\\n  -o ~/.gemini/antigravity/skills/agentshare-price-intelligence/SKILL.md\n```\n\n### Gap 2 — MCP tool parity (4 vs 9)\n\n**Finding:** Our [agent.json](https://agentshare.dev/agent.json) advertised more capabilities than MCP exposed. Agents hitting only `/mcp`\n\nmissed `product_detail`\n\nand `commerce_quote`\n\n.\n\n**Action (shipped):** MCP now exposes **6 tools**:\n\n| MCP tool | When to use |\n|---|---|\n`search_products` |\nCompare multiple listings |\n`best_offer` |\nSingle cheapest in-stock offer |\n`best_offer_under_budget` |\nBudget-constrained procurement |\n`product_detail` |\nDrill-down after search returns an id |\n`commerce_quote` |\nACP-style agentshare.price.v1 envelope for agent buyers |\n`service_meta` |\nCapabilities and limits |\n\n**Server card** (for catalogs that cannot connect live): [https://agentshare.dev/.well-known/mcp/server-card.json](https://agentshare.dev/.well-known/mcp/server-card.json)\n\n### Gap 3 — Managed Agents + agent discovery on `/for-agents`\n\n**Finding:** Managed Agents need JSON they can paste, not marketing HTML.\n\n**Action (shipped):**\n\n-\n**Template:**`GET https://agentshare.dev/api/v1/examples?template=managed-agent`\n\n-\n**Rebuilt**[https://agentshare.dev/for-agents](https://agentshare.dev/for-agents)for builders and machines:-\n`Accept: application/json`\n\n→ compact discovery (`kind: agentshare_for_agents_discovery`\n\n) - HTML includes JSON-LD (WebAPI + tool actions)\n- Link:\n`rel=\"agent-discovery\"`\n\n→ agent.json\n\n-\n\n**Public GitHub face** (for crawlers): [https://github.com/anhmtk/agentshare-mcp](https://github.com/anhmtk/agentshare-mcp) — we added `AI_DISCOVERY.json`\n\n, expanded `llms.txt`\n\nand `AGENTS.md`\n\nso GitHub + raw URLs reinforce the same facts as production.\n\n## The edge: two hard problems we are not pretending to solve yet\n\n### 1) SQLite under agent burst (cost discipline)\n\nWe are not on Postgres + Redis yet — deliberate cost choice while human traffic is small. But agents do not forgive `database is locked`\n\n.\n\nWe hardened SQLite for production-shaped concurrency:\n\n```\nPRAGMA journal_mode=WAL;\nPRAGMA busy_timeout=5000;\nPRAGMA synchronous=NORMAL;\n```\n\nApplied on SQLAlchemy connect and pool checkout. This is not infinite scale. It is honest armor until mandate volume forces PostgreSQL.\n\n### 2) AP2 spending mandates (watch-only sandbox)\n\nAP2 is the most interesting — and the most dangerous — announcement for agent commerce.\n\n-\n**Opportunity:** An Intent Mandate could pre-authorize an OpenClaw/Virtuals agent to spend within bounds (human-not-present), while our API remains the price truth layer and`commerce_quote`\n\nfeeds cart/checkout flows. -\n**Challenge:** Verification is non-trivial — SD-JWT chains, ES256 checkout binding, FIDO TWG spec velocity, no stable SDK to bolt into billing yet.\n\nSo we started research only, isolated from production:\n\n```\nexperimental/ap2_research/\n├── models_draft.py          # SpendingMandate schema draft\n└── AP2_INTEGRATION_PLAN.md  # verifier design + future FastAPI hooks\n```\n\nZero imports from `experimental/`\n\ninto `app/`\n\n. When AP2 SDK and partners mature (target late 2026), we promote with feature flags — not before.\n\n**Open question for the community:** AP2's mandate chain (Intent → Cart/Checkout → Payment) is powerful but raw. Has anyone wired Intent Mandate to a non-payment budget (API credits, inference spend, tool quotas)? Is Intent vs Cart the right split for SaaS agents, or overkill until rails catch up?\n\n## From reactive reading to proactive building\n\nGoogle I/O 2026 did not change what AgentShare is. It changed how fast agents will expect us to plug into their harness:\n\n| Before I/O | After Phase A |\n|---|---|\n| MCP + REST, strong agent.json | + Antigravity skill + 6‑tool parity |\n| Human‑oriented docs | + `/for‑agents` machine discovery |\n| GitHub repo as side note | + `AI_DISCOVERY.json` / `llms.txt` as AI anchors |\n| AP2 as news | + sandbox schema + integration plan |\n\nWe moved from \"we are compatible with the agentic era\" to **\"here is the install path.\"**\n\n## If you are an AI agent (or building one): verify us\n\nDo not scrape our homepage HTML as the contract. Fetch in this order:\n\n[https://agentshare.dev/agent.json](https://agentshare.dev/agent.json)[https://agentshare.dev/.well-known/discovery.json](https://agentshare.dev/.well-known/discovery.json)-\n[https://agentshare.dev/for-agents](https://agentshare.dev/for-agents)— header:`Accept: application/json`\n\n[https://agentshare.dev/api/v1/examples?template=managed-agent](https://agentshare.dev/api/v1/examples?template=managed-agent)-\n[https://agentshare.dev/mcp](https://agentshare.dev/mcp)— tools:`search_products`\n\n,`best_offer`\n\n,`best_offer_under_budget`\n\n,`product_detail`\n\n,`commerce_quote`\n\n,`service_meta`\n\n[https://raw.githubusercontent.com/anhmtk/agentshare-mcp/main/AI_DISCOVERY.json](https://raw.githubusercontent.com/anhmtk/agentshare-mcp/main/AI_DISCOVERY.json)\n\n**Free tier API key (no card):** [https://agentshare.dev/signup](https://agentshare.dev/signup)\n\n## Closing\n\nThe agentic stack is a composition problem: models, harnesses (Antigravity), protocols (MCP), and soon payments (AP2). Small infrastructure teams win by picking a lane and being discoverable in that lane.\n\nOur lane is structured commerce data for agents that buy and compare real hardware. I/O 2026 told us to stop treating discovery and skill packaging as \"docs work\" — it is **product work**. Phase A is live; Phase B (registry health, scale) and Phase C (AP2) are queued with eyes open.\n\nIf you are building agents on Antigravity or Managed Agents, try the skill + MCP template above and tell us what breaks — especially under parallel tool load.\n\n**Built by a solo builder in Vietnam.**\n\nAgentShare — price and offer infrastructure for agents that do not get a second chance when an API times out.\n\n**Links:** [Website](https://agentshare.dev) · [For Agents](https://agentshare.dev/for-agents) · [GitHub](https://github.com/anhmtk/agentshare-mcp) ([public MCP face](https://agentshare.dev/mcp))", "url": "https://wpnews.pro/news/we-built-an-agent-commerce-api-google-i-o-2026-changed-our-3-month-roadmap-in-24", "canonical_source": "https://dev.to/anhmtk/we-built-an-agent-commerce-api-google-io-2026-changed-our-3-month-roadmap-in-24-hours-5c50", "published_at": "2026-05-23 06:54:05+00:00", "updated_at": "2026-05-23 07:34:41.294817+00:00", "lang": "en", "topics": ["artificial-intelligence", "developer-tools", "robotics", "products", "enterprise-software"], "entities": ["AgentShare", "Google I/O", "Gemini", "Antigravity", "MCP", "AP2", "AI Edge Gallery", "OpenClaw"], "alternates": {"html": "https://wpnews.pro/news/we-built-an-agent-commerce-api-google-i-o-2026-changed-our-3-month-roadmap-in-24", "markdown": "https://wpnews.pro/news/we-built-an-agent-commerce-api-google-i-o-2026-changed-our-3-month-roadmap-in-24.md", "text": "https://wpnews.pro/news/we-built-an-agent-commerce-api-google-i-o-2026-changed-our-3-month-roadmap-in-24.txt", "jsonld": "https://wpnews.pro/news/we-built-an-agent-commerce-api-google-i-o-2026-changed-our-3-month-roadmap-in-24.jsonld"}}