Use the API with AI tools

An AI agent with your key can draft, illustrate, schedule and publish content for you. The API was designed for this: it has an OpenAPI document that agents can read, an llms.txt index of these docs, a clean Markdown copy of every page, and a ready system prompt.

Which tool, and how

Rules every agent should follow

These are built into the system prompt. Paste it into your tool so you do not have to repeat them:

1. Read the key from UND_API_KEY, never print it. The agent should never echo, log or write the key, and never put it in a URL.
2. Confirm before publishing. Public content goes out under your name. Ask the agent to show a preview and wait for your yes, unless you said otherwise.
3. Upload images first, then use data.url. See Upload images.
4. Look ids up, never invent them. Communities, categories, job options and places come from the lookups.
5. Send an Idempotency-Key on every create, so a retry never posts twice.
6. Schedule in UTC with Z, between 5 minutes and 180 days ahead, and say both times back to you.
7. Handle errors properly. On 422, fix the named fields. On 429, wait Retry-After and report the remaining quota.
8. Finish with links. Return the web_url of everything created.

Give each agent its own key

Create one key per tool, with only the scopes it needs, and a short expiry. Then API analytics shows what each agent did, and you can revoke one without touching the others.

Next steps

• Claude Codeset the key, add a CLAUDE.md note, allow curl.
• Codex CLIset the key, AGENTS.md, and turn on network access.
• ChatGPT Actionsimport the OpenAPI URL and keep the GPT private.
• System promptthe copy-paste rules for any agent.
• Prompt recipesprompts that work well.
• Claude Desktopwhat it needs, and what to use meanwhile.