Build guides with the agent you already use.
Sceniq sells travel guides that open as interactive maps. Each guide is made by one creator who has been to the places in it. The creator API lets that creator's own AI agent do the structuring work: spots with their facts, chapters, routes, places to stay and eat, photos and the sales page, from the creator's notes, map links, tracks and photos. The creator reviews every spot and decides what goes live.
Who it is for
- Creators who want Claude, Cursor, Codex or another agent to draft a guide from their own material.
- Developers a creator works with, who script imports or keep a guide in sync with another system.
A key belongs to one creator and reaches only that creator's guides. There is no API for buyers, the store or other creators.
REST and MCP, one API
Every operation exists twice with the same name, the same input and the same answer:
| REST | MCP | |
|---|---|---|
| Endpoint | https://sceniq.earth/api/v1 | https://sceniq.earth/api/mcp |
| An operation is | a path and method: POST /v1/guides/{productId}/spots | a tool: create_spot |
| Best for | scripts, imports, anything with an HTTP client | agents: Claude Code, Claude Desktop, Cursor, Codex |
| Errors | { error: { code, message } } with an HTTP status | a tool result with isError and the same code |
Photo uploads are the exception: they are plain HTTP requests (raw bytes or multipart), so they exist over REST only. Agents connected over MCP upload with a short HTTP call; Photos shows how.
What an agent can and cannot do
The agent is the creator's assistant, not the author. It can create and edit everything that makes up a guide, check links, run the readiness check and, with a key that has the publish option, publish a live guide's changes when the creator asks. Some steps always stay with the creator in the studio: putting a new guide on sale, publishing the sales page, store visibility, prices under an outdated agreement, payouts and the account. API keys and scopes has the full list.
Where to go next
- Quickstart: a key, the first request, the first guide.
- Connect an agent: setup for Claude Code, Claude Desktop, Cursor and Codex.
- Build a guide with an agent: the workflow that works, step by step.
- API reference: every operation with its parameters, response fields, an example and its errors.