> ## Documentation Index
> Fetch the complete documentation index at: https://crevio.co/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Crevio for developers

> Build on the AI-native platform that runs your business — REST API, TypeScript SDK, and an MCP agent surface you can just talk to.

**Crevio is an AI-native, all-in-one platform that runs your business — and everything it does is available to you as a REST API, a typed SDK, and an agent you can talk to.**

You describe what you want to sell and Crevio builds, launches, and grows it. For developers that means three surfaces over the same primitives: a REST API at `https://api.crevio.co/v1`, the official [`@crevio/sdk`](/developer/guides/sdk) TypeScript client, and an [MCP](/developer/mcp) endpoint that exposes the platform to AI agents.

<Note>
  **The AI-native thesis:** almost anything you can do with the API, you can also just *ask* Crevio's agent to do over MCP — "launch a paid course", "research my competitors and draft three posts", "spin up a landing page". The agent and the API share the same primitives, so you can mix scripted calls with delegated work.
</Note>

## Pick your path

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/developer/guides/quickstart">
    **Pick this if you just got an API key.** Go from zero to your first successful call — and your first product — in under five minutes.
  </Card>

  <Card title="Build a custom website or checkout" icon="code" href="/developer/guides/sdk">
    **Pick this if you're a frontend or full-stack dev** building your own buying experience. Use `@crevio/sdk` to read products and create checkouts; payments stay on Crevio's rails.
  </Card>

  <Card title="Run an AI agent (Tasks & MCP)" icon="robot" href="/developer/mcp">
    **Pick this if you want autonomous work**, not just CRUD. Schedule Tasks (your AI workforce) or wire Crevio's MCP into your own agent.
  </Card>

  <Card title="Generate content with AI" icon="wand-magic-sparkles" href="/developer/guides/usage-billing">
    **Pick this if you're building content tooling** — images, video, audio, web research, and social posts via metered pay-per-call endpoints.
  </Card>

  <Card title="Sync data & webhooks" icon="arrows-rotate" href="/developer/guides/webhooks">
    **Pick this if you're integrating Crevio with another system.** List and paginate resources, then react to events with signed webhooks.
  </Card>

  <Card title="Conventions & gotchas" icon="triangle-exclamation" href="/developer/guides/conventions">
    **Read this before you write code.** Unwrapped params, association ids, creation order, money in cents — the rules that prevent most first-day errors.
  </Card>
</CardGroup>

## Start here

<CardGroup cols={2}>
  <Card title="Quickstart" icon="bolt" href="/developer/guides/quickstart">
    Key to first call, fast.
  </Card>

  <Card title="Conventions" icon="list-check" href="/developer/guides/conventions">
    The request and response rules every endpoint follows.
  </Card>

  <Card title="API reference" icon="code" href="/developer/api-reference/introduction">
    Every endpoint, parameter, and schema — auto-generated.
  </Card>

  <Card title="MCP & agents" icon="plug" href="/developer/mcp">
    Let an AI agent drive Crevio.
  </Card>
</CardGroup>
