AI agents can already browse catalogs, compare plans and prepare carts—if the host publishes machine-readable APIs. EuroVDC does: public MCP, OpenAPI and a Phase 1 agent checkout that returns a browser checkout_url so a human can finish payment. This is agent-commerce for Sofia (EU) hosting, not sci-fi “the bot charged your card alone.”
Start from for-agents, the manifest at /.well-known/mcp.json, then product pages for web hosting and cloud server.
What agents can discover
- Live catalog: MCP tools and OpenAPI expose domains, TLDs, hosting and cloud SKUs with EUR pricing—no HTML scraping.
- Recommendations: Tools such as
recommend_server/ list-products style calls help narrow plans for a stated workload. - Cart handoff:
agent_cart_add(API or MCP) builds a cart and returnscheckout_urlfor the user browser (Phase 1). Cart TTL is finite (typically 24 hours). - Optional quotes: Locked quotes may exist before handoff; treat payment completion as a human (or later Phase 2/3 Stripe path when enabled)—do not assume silent autonomous card charging.
Practical agent-commerce flow
- Load MCP manifest or import OpenAPI into your agent / Custom GPT Actions.
- Call catalog or recommend tools with language set (
lang=enetc.). - Pick a product_id / billing cycle (or domain + required fields for ccTLDs).
- Add to cart; open
checkout_urlfor the human to authenticate and pay. - Fulfillment follows normal order status—agents can poll status tools when available; provision still depends on paid order.
Phase 1 is deliberate: discovery and cart are machine-speed; money movement stays where liability and SCA/3-D Secure live—usually the browser. That split keeps agent UX fast without inventing unattended card charging that the public API does not promise today.
Partner keys raise rate limits for serious integrations; public tier still works for discovery. Never paste secrets into shared prompts—scope keys to the agent runtime that calls MCP or OpenAPI.
Why Sofia EU matters for agents
EuroVDC infrastructure lives in Sofia (EU). Agents that recommend “EU residency” or GDPR-friendly hosting can point to a concrete EEA location without inventing a Western-hub story. Pair that with honest product CTAs: brochure sites on hosting; root/Docker/API stacks on cloud.
Human vs agent responsibilities
- Agent: discover prices, check TLD fields, assemble cart, return checkout link, later check status.
- Human: approve payment method, complete SCA, accept terms, own the account.
- Operator: keep API keys (partner tier) scoped; never paste secrets into public prompts.
Docs stay on /en/for-agents and agents.md. Product buyers still land on web hosting or cloud server when humans prefer a classic path.
Frequently asked questions
Can an agent pay without a human?
Phase 1 returns a browser checkout_url—expect human payment completion. Later Stripe/prepare paths may exist when enabled; do not assume unattended card charging by default.
MCP or OpenAPI—which first?
Claude/MCP clients: mcp.json then /mcp. ChatGPT Actions: import openapi.json. Both read the same live catalog idea.
Do agents see real EUR prices?
Yes—public catalog tools expose live pricing; confirm billing cycle and any promo rules at checkout.
Where do servers run?
EuroVDC hosting and cloud footprints are Sofia (EU).
What should I buy after the agent recommends?
Simple sites: web hosting. Root/custom stacks: cloud server. Dedicated only when metrics demand it.
Where is the agent documentation?
Use for-agents, agents.md and /.well-known/mcp.json—then product CTAs for hosting/cloud.
