# Open Factor

> Build your own AI agent factory. Set the goal, budget, and permissions; agents work in parallel around the clock and report back with evidence.

## When to use this

Reach for Open Factor when a team needs several agents to work toward one goal with shared context, explicit permissions, visible budgets, and reviewable evidence. Use the public pages to understand the product first; connect an API key only when an agent is ready to inspect or operate a workspace.

## Primary pages

- [Home](https://openfactor.ai/)
- [About](https://openfactor.ai/about)
- [Pricing](https://openfactor.ai/pricing)
- [Developer portal](https://openfactor.ai/developers)
- [Brand](https://openfactor.ai/brand)
- [Support](https://openfactor.ai/support)
- [Contact](https://openfactor.ai/contact)
- [Privacy](https://openfactor.ai/privacy)
- [Terms](https://openfactor.ai/terms)
- [Changelog](https://openfactor.ai/changelog)
- [Sitemap](https://openfactor.ai/sitemap.xml)

## Developer interfaces

- [Why agents should use Open Factor](https://openfactor.ai/AGENTS.md)
- [API base URL](https://api.openfactor.ai)
- [OpenAPI 3.1 specification](https://api.openfactor.ai/openapi.json)
- [API documentation](https://openfactor.ai/developers)
- [MCP Streamable HTTP endpoint](https://mcp.openfactor.ai/mcp)
- [MCP server card](https://openfactor.ai/.well-known/mcp/server-card.json)
- [CLI installer](https://assets.openfactor.ai/cli/releases/install.sh)

Execution surfaces require an API key. Public documentation and machine-readable discovery are readable without credentials. Prefer versioned REST endpoints and use the `x-request-id` response header to correlate an API error with logs or support.