Agentic commerce in Bulgaria

Yes, agentic commerce already works in Bulgaria. Brand Design Ltd. in Varna sells its services to AI agents through open protocols: an agent can find the offer, place an order and pay, and for fixed-price services nobody on our side has to step in.

On 21 September 2026 an outside AI agent did exactly that in a public test, and the verifier returned PASS. Below is everything that runs today, each item with the public address where you can check it yourself. Last checked on 13 October 2026.

The public test

An outside participant gave their AI agent a neutral task with the service code 101Ts3t and a budget of EUR 1.00. The task named no merchant, website or payment link. The agent found the offer on its own, ordered it and paid EUR 0.99 with its authorised wallet. The public verifier checked discovery, payment and fulfilment and returned PASS.

As of 21 September 2026, this is Bulgaria’s first publicly proven operational open agentic-commerce system.

Public PASS verification record

Test rules, published before the test

Signed proof files and GitHub/Sigstore attestation

What runs today

Direct commerce API

The bd-commerce/1 API gives any agent our manifest and catalogue. An agent can register itself without a prior contract, signs its requests with HMAC and can order, accept an offer and pay.

The manifest

UCP

Our Universal Commerce Protocol profile is published on the merchant’s own domain, branddesign.ltd, in two versions: 2026-08-25 and 2026-04-08. The checkout accepts Stripe shared payment tokens. Google Pay is connected in test mode until Google approves the integration.

The UCP profile

AP2 mandates

Since 9 October 2026 the UCP checkout accepts AP2 checkout mandates. We sign the checkout, and before any charge we verify the mandate: the issuer’s signature, the holder’s signature and whether the amounts and lines match. Payment mandates and open mandates are not accepted.

ACP

The Agentic Commerce Protocol profile uses the same catalogue and the same order records as the direct API.

The ACP profile

MCP

Our MCP server at branddesign.ltd/mcp is listed in the official MCP Registry as ltd.branddesign/commerce. Through it an agent reads the catalogue, creates an order, accepts an offer, starts the payment and checks the status.

The MCP Registry entry

WebMCP and CLI

In a browser that supports WebMCP, every page of this site registers seven read-only tools: services, prices, the catalogue, evidence and capabilities. A command-line client gives the same reads. Neither can order or pay.

WebMCP and CLI documentation

Agent check (KYA)

A self-registered agent proves control of its contact domain with a DNS record before it pays on its own with a payment token. The same check applies to agents that sign in through UCP. It confirms the domain, not the buyer’s identity or permission to spend.

Payment tied to the accepted offer

An agent pays only for an offer that has been accepted with a concrete amount. Each offer is bound to a stored copy of the page and terms it came from. If the catalogue changes, offers that have not yet been accepted stop being valid.

How we keep a payment tied to an accepted offer

The permanent record

The implementation is archived with a DOI. Version 1.4, published on 29 September 2026, covers the direct channel, the ACP and UCP routes, the domain check and the signed route evidence. Version 1.3 holds the public PASS. AP2 mandates, the UCP profile on branddesign.ltd and WebMCP on every page came after version 1.4.

DOI 10.5281/zenodo.23038829

Version 1.3 with the public PASS

Written about it

Nikola Mishev described how we protect autonomous payments on LinkedIn, and our team explained the link between offer and payment on DEV Community. DokuTrak, an outside author, uses Brand Design Ltd. as an example in its article on visibility to AI agents. Our Clutch portfolio lists the gateway as a project.

LinkedIn, 30 September 2026

DEV Community, 30 September 2026

DokuTrak, 29 September 2026

Clutch portfolio: B2A Agentic Commerce Gateway

What this record does not claim

Google Pay runs in test mode. Being open to agents is not admission to the checkout programmes of Google or OpenAI; that depends on their approval. The public PASS covers the direct path from 21 September, and new real tests are still needed for the protocol routes added since then.

Related pages

Frequently asked questions

Is there agentic commerce in Bulgaria?

Yes. Brand Design Ltd. in Varna sells to AI agents through UCP, ACP, MCP and its own API, and on 21 September 2026 an outside agent made a real purchase in a public test that returned PASS.

Can an AI agent order and pay without a person?

Yes, for services with a fixed price in the catalogue. The agent pays with a shared payment token after the domain check, or the buyer completes a hosted checkout. For services that need a project quote, we set the final amount first.

How can I check this myself?

Every item on this page links to a public address: the UCP profile, the MCP Registry entry, the test record and the DOI. They open without an account.