Start Here
Start Here
The fastest path to understand Agent Mag APIs, credits, dashboard surfaces, and docs context.
This section sets the baseline for every Agent Mag integration: which base URL to use, how auth works, how credits apply, and how docs context can be copied into local agent workspaces.
Status
| Area | Status | Notes |
|---|---|---|
| Docs site | Available | https://docs.agentmag.dev mirrors the /docs app route. |
| Copy page context | Available | Markdown, text, JSON, agent prompt, command, and URL formats. |
| Docs context CLI | Available | npx agentmag add docs <slug> writes local docs context. |
| Web Intelligence API | Preview | Scrape is the first endpoint; crawl, extract, and screenshot are documented as preview/planned surfaces. |
| Creative APIs | Planned | Product specs for image and social generation workflows. |
Core Concepts
| Concept | Meaning |
|---|---|
| Workspace | The account or team boundary that owns API keys, jobs, usage, and credits. |
| API key | Bearer token used by hosted Agent Mag APIs. Keys should be scoped and rotated from the dashboard. |
| Credits | Shared usage wallet for hosted APIs, premium assets, and future tools. |
| Docs context | First-party content that agents can copy or install locally; not a skill bundle. |