For AI Agents
AI agents and developer access
Outfame has a public, read-only interface for AI agents and developers. It answers four questions without an account or an API key: what the plans are and what the first month costs, which free tools exist, which blog articles cover a topic, and how a person signs up. Everything below is live at www.outfame.com.
Prices are always first-month prices in US dollars. The first month of the selected plan is billed at signup, there are no contracts, and you can cancel anytime.
What you can use
| Interface | Address | What it does |
|---|---|---|
| REST API | https://www.outfame.com/api/agents/v1 | JSON for plans, free tools, blog search and a health check. |
| MCP server | https://www.outfame.com/mcp | Five read-only tools over Streamable HTTP, stateless, no authentication. |
| A2A agent | https://www.outfame.com/a2a | Ask in plain language; the reply is one message with a text part and a data part. |
| OpenAPI 3.1 | https://www.outfame.com/openapi.json | The machine-readable description of the REST API. |
| WebMCP | outfame.com marketing pages | In browsers that support WebMCP, the page offers five tools to the visiting agent. |
Pages in this section
- MCP server: the public MCP server at /mcp: protocol versions, the five tools and their inputs, client setup and errors.
- A2A agent: the A2A endpoint at /a2a: both message methods, the five skills with example questions, the reply format and errors.
- REST API for agents: the read-only JSON endpoints under /api/agents/v1, their parameters, response fields and the OpenAPI file.
- Account access for agents: reading a user's own account with their approval: OAuth 2.1, auth.md agent registration, the account API and the account MCP server.
- Discovery files: the llms.txt, robots.txt and /.well-known files that let agents find these interfaces.
Sign up
A person starts at https://www.outfame.com/setup: connect an account by its username (Outfame never asks for a password) and select a plan.