Determ API

Appearance

Develop with AI ​

These docs are designed to be AI-friendly. Every page is structured so that AI assistants -- ChatGPT, Claude, Cursor, GitHub Copilot, and others -- can understand the Determ API and help you write integration code, debug issues, and build features faster.

Four ways to use AI with these docs ​

1. Quick copy-paste ​

Every API endpoint page has a "Copy page for AI" button at the top. Click it to copy the entire page content in a format optimized for AI consumption. Then paste it into your AI assistant along with your question.

This is the fastest approach when you are working with a single endpoint and need help with a specific task.

2. Full context file ​

For comprehensive coverage of the entire API, use the AI Context File. It contains a single block with every endpoint, request/response schemas, enums, and conventions. Copy it once, paste it into your AI chat, and the assistant will have everything it needs to help you build a complete integration.

Best for: starting a new project, building multi-endpoint workflows, or when you want the AI to choose the right endpoint for your use case.

3. Workflow prompts ​

The Workflow Prompts page has six ready-made prompts for common tasks: exploring the API, scaffolding a project, building a dashboard, debugging, writing tests, and reviewing code.

Best for: getting started quickly with a proven prompt structure rather than writing your own from scratch.

4. OpenAPI spec ​

For code generation and exact type information, point the AI at the machine-readable spec:

https://developers.determ.com/openapi.json

Most coding agents can fetch that URL themselves. It gives the assistant every request and response shape verbatim, which cuts down on invented fields. See the OpenAPI Spec page.

Best for: generating typed clients, request builders, and response models — or pairing with the context file so the AI has both the shapes and the conventions.

IDE integration ​

If you use an AI-powered IDE, you can give it persistent knowledge of the Determ API by adding a rules file to your project root. This way, the AI assistant automatically has API context every time you ask a question in that project.

Create the file your tool reads — .cursorrules for Cursor, CLAUDE.md for Claude Code — with the same content:

# Determ API Integration Rules

Base URL: https://api.mediatoolkit.com
Auth: Bearer token in Authorization header
OpenAPI spec: https://developers.determ.com/openapi.json

Key endpoints:
- GET /v2/me — Current user
- POST /v2/organizations/{orgId}/keywords/{keywordId}/mentions/count — Count mentions by keyword
- POST /v2/organizations/{orgId}/keywords/{keywordId}/mentions/scroll — Scroll mentions by keyword
- POST /v2/organizations/{orgId}/keywords — Create keyword

Always use scrollToken for pagination. Use publishedTime.relative for time ranges.

TIP

For maximum AI effectiveness, copy the full context block from the AI Context File page and paste it into your rules file instead of the summary above. The summary covers the basics; the full context file covers every endpoint, every field, and every enum.

Next steps ​

Built by Determ — Media Monitoring & Analytics