# Build on the API

A developer's first week in order, from creating a key in the Developer Hub to reacting to platform events with a webhook and copying a cookbook.

This path is a developer's first week with the platform. It starts in the Developer Hub, where one key serves REST, the SDK and MCP, makes a first call, then adds a library, points a coding agent at these docs, wires a webhook, and ends with a cookbook you can copy into your own code. Each page stands alone once you have a key, so you can also jump to the one you need.

**Who this path is for:** any developer with a Katonic account whose administrator has enabled the public API for the tenant.

## After the path

The cookbooks continue where the last step leaves off: checking that an agent answers, gating a publish on an evaluation, governing a tool with an approval, knowing which model served your call, matching a question to a known answer, reacting to an evaluation with a webhook, remembering a conversation, reporting on spend and usage, turning production traces into a dataset, extracting records from your documents, asking a knowledge graph, and building a coding agent on the harness. Take them as your work needs them; the Cookbooks tab lists them all.

## Related

- [Learn the API by path](/learn/overview)
- API overview
- Cookbooks

Source: https://docs.katonic.ai/learn/developers
