For AI Agents
REST API for agents
Base URL: https://www.outfame.com/api/agents/v1. Every endpoint is a GET that returns JSON and allows requests from any origin. No key is needed. A GET on the base URL itself lists the endpoints.
The machine-readable description is the OpenAPI 3.1 file at https://www.outfame.com/openapi.json.
Endpoints
| Endpoint | Returns |
|---|---|
GET /plans | The plans Go, Grow and Glory: name, first-month price in US dollars, what each includes and the sign-up link. |
GET /free-tools | Each free Instagram and AI tool: name, page URL and a one-line description. |
GET /blog/search?q=&limit= | Blog articles matching the words in q: title, URL, description, publish date and categories. |
GET /health | The status of the API, {"status":"ok"}. Never cached. |
The signed-in user's own account summary is at GET /me; it needs the user's approval and is described on the account access page.
Blog search parameters
| Parameter | Rules |
|---|---|
q | Required. 2 to 100 characters. Matched against article title, description, tags and category. |
limit | Optional. A whole number from 1 to 10. Default 5. |
A missing or out-of-range parameter returns status 400 with {"error":{"code":"invalid_request","message":"..."}}. Responses are cacheable except /health.
Blog search allows 30 searches a minute per IP address, one budget shared with the MCP server and the A2A agent. Above it the endpoint returns status 429 with error code rate_limited; retry after a minute.
Response fields
Plans
GET /plans returns currency (USD), a note on how the prices work, and plans, one object per plan:
| Field | Meaning |
|---|---|
id | The plan name in lower case: go, grow or glory. |
name | The plan name as shown on the site. |
firstMonthPriceUsd | The first-month price as a number. |
firstMonthPrice | The same price as text, for example $49. |
summary | A one-line description of the plan. |
includes | The plan's features, as listed on the pricing page. |
signupUrl and pricingUrl | Where a person signs up and the pricing page. |
Free tools
GET /free-tools returns tools, each with name, url and description.
Blog search
GET /blog/search returns the query it searched for, the total number of matching articles and results, each with title, url, description, publishedAt and categories.
Examples
curl https://www.outfame.com/api/agents/v1/plans
curl https://www.outfame.com/api/agents/v1/free-tools
curl "https://www.outfame.com/api/agents/v1/blog/search?q=instagram%20hashtags&limit=3"
curl https://www.outfame.com/api/agents/v1/healthThe same data is available as MCP tools and through the A2A agent, which answer from the same functions.
Pages in this section
- AI agents and developer access: what the agent interfaces are and where each one lives.
- 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.
- 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.