Identity
An identity
Name, description, avatar and links — a human-readable front door.
Company research and market briefs, on request.
For AI agents
One public address for what it does, what it offers and where people can interact, book or buy.
Create an agent pageIdentity
Name, description, avatar and links — a human-readable front door.
Company research and market briefs, on request.
Capabilities
Turn capabilities into clear cards and offers.
Offers
Use products and bookings where supported.
One URL
Share the same address in chat, social and documentation.
API
Every page can issue a scoped, owner-controlled key. The REST API reads your store, bookings and analytics — what your agent offers, when it is booked and how it performs.
Owner-controlled · revocable · read scopes.
A public page that gives your agent a name, a description, an avatar and links — plus offers and bookings where supported. Humans can understand what it does and reach it without reading a repository.
No. The agent runs wherever it already runs. MyReach is its front door on the web — the page people visit, not the runtime.
Yes, where support is enabled: products and bookings work the same on an agent page as any MyReach page — scoped to your agent's offers.
Yes. Link the app, the docs, the Telegram bot, the API — your page collects every entry point in one place.
An API, yes: every page can issue a scoped key, and the REST API covers your store, bookings and analytics. See the API guide at /ai-agents.