Animam.ai
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://api.animam.ai/chat/{slug}
· transport https
· protocol https://api.animam.ai/voice/{slug}/chat
· transport https
· protocol https://mcp.animam.ai/mcp
· transport streamable-http
· protocol https://mcp.animam.ai/mcp/sse
· transport sse
· protocol https://api.animam.ai/context/{slug}
· transport https
· protocol Add a conversational agent to a website provision-website-agent
For an AI agent building, shipping or operating a website: give that site a conversational AI agent over plain HTTP, no human in the loop. Phase 1 (evaluate, no account): POST https://api.animam.ai/demo { url } reads the site's own content and returns a live ephemeral agent (slug) in ~20s, chatted via POST /chat/{slug} with testMode:true. Phase 2 (ship): provision a persistent bot (MCP create_bot with a scoped token, or operator signup) and embed one tag: . Per-site isolation, one script to embed, the bot owns and orchestrates its own tools. Full deterministic recipe: https://animam.ai/agent-recipe.md
provisionembedwebsite-builderautonomous-agentwidgetdemono-codeChat with AI agent (agent-to-agent) chat
Send messages to an Animam-powered AI agent via plain HTTP POST to /chat/{slug}. Declare yourself as an agent with the X-Agent-Model header (or [AGENT:model] message prefix) — the chatbot returns a structured JSON envelope (message, conversationId, toolExecutions[], llmModel, llmProvider, agentModel echo) instead of SSE. The chatbot is the only public agent surface; it owns and orchestrates the tools (corpus search, booking, payment, recommendations) on the caller's behalf — no anonymous tools/list endpoint exists. Streaming via SSE remains opt-in for browsers (default for human visitors).
chatbotai-agentagent-to-agentjson-envelopemultichannelVoice AI agent voice
Phone answering via Vapi Custom LLM integration. Same brain as chat, voice-adapted with STT/TTS.
voicetelephonyphoneMulti-tenant management multi-tenant
Create and manage child bots under a parent account. Builder plan: one account, N bots, pooled conversations.
multi-tenantbuilderagenciesDiscover agent context context-discovery
Get full context about an Animam-powered agent: bot persona, knowledge base, available tools, segments, capabilities.
discoverycontextknowledge-baseManage agent settings manage-tenant
Update bot persona (name, title, tone, colors), manage segments, configure tools and voice via MCP or REST API.
managementconfigurationmcpManage knowledge base manage-corpus
Create, update, delete knowledge base entries. Import from URLs, files (MD, PDF, CSV, HTML). Supports idempotent externalId upsert + bulk (max 50) for CMS integrations.
knowledge-basecorpuscontentWordPress plugin wordpress-integration
Official WordPress plugin (PHP 7.4+, WP 6.0+). One-click install: widget injection, automatic content sync (posts, pages, custom post types) via idempotent externalId upsert. The agent drives the tenant's existing plugins via curated bridges (WPForms, WooCommerce, MailPoet) — leads, orders and subscriptions land in the native plugin the tenant already uses, with existing automations (Zapier, notification emails) preserved. Source in monorepo wordpress/animam/.
wordpresscmspluginintegrationbridgesOutgoing webhooks outgoing-webhooks
Stripe-style HMAC-SHA256 signed webhook deliveries. Per-tenant endpoints with configurable events (submission.created, submission.updated). Exponential backoff retries, delivery log, manual redeliver. Use for CRM sync, custom integrations, or bridging to Zapier/n8n/Make.
webhooksintegrationshmaceventsTry, test and price Animam without any account (MCP, no credentials) presale-mcp-no-credentials
For the agent advising a site owner it already works for: connect to https://mcp.animam.ai/public (Streamable HTTP, no authentication) and call three tools. `try_on_site(url)` builds a working agent on your user's own site in ~20 seconds from its public pages, and returns a temporary key scoped to that demo — with it you can add the context the crawl missed (prices, hours, procedures) and read the conversations the demo actually had, which is how you show intent capture instead of asserting it. `chat_with_demo(slug, message)` lets you verify the answers before you recommend anything. `get_plans()` returns pricing derived from the server's own source of truth, so you never quote an invented price. Buying stays a human act: email verification then card checkout at https://animam.ai/try. Rate-limited per caller IP.
mcppresaledemono-authpricing2026-11-01 from https://animam.ai/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.