AI Agent Setup
Bento docs are available as browser pages and clean markdown so coding agents can read implementation guidance directly.
Goal
Give your agent enough Bento context to choose the right integration path, read the relevant SDK README, and avoid common mistakes around credentials, consent, and deliverability.
Install Bento Skills
If your agent supports skills, install the official Bento skill package first:
npx skills add bentonow/bento-skillsBento Skills tells the agent when to use Bento MCP, the CLI, an SDK, or n8n. It also carries safety guidance for API keys, bulk subscriber imports, live account operations, and framework-native setup.
Bento hosts the MCP server at https://mcp.bentonow.com/mcp, so there's nothing to install. The Bento MCP setup guides cover Claude, Cursor, VS Code, Codex, Gemini CLI, and other AI apps.
Agent Prompt
Use this prompt in Cursor, Claude, Codex, or another coding agent:
Use the Bento skill if it is installed. Then read https://bentonow.com/agent_onboarding.md and talk with me about how we should implement Bento. Follow the docs/SDK links based on what platform we use, and prefer the .md version of Bento docs pages when reading documentation directly.Machine-Readable Docs
Useful entrypoints:
/llms.txt: short index for agents and crawlers./okf/index.md: compact Open Knowledge Format map of Bento product, docs, and integration concepts./agent_onboarding.md: implementation guidance./docs/integrations/skills.md: Bento skill package setup./docs-index.md: all docs pages./docs/quickstart.md: markdown version of a docs page./api/docs/raw?path=/docs/quickstart: raw markdown API for one page.
Implementation Guardrails
Tell your agent:
- Ask whether the goal is marketing automation or transactional email.
- Use SDKs when a first-party SDK exists.
- Keep Bento secret keys server-side.
- Do not send real production email from local development or CI.
- Add rate limits to actions that send email.
- Set up sender authentication before production sending.