canonical: https://jentic.com/apis/adako.ai/adako # Adako REST API The Adako API gives an AI assistant one HTTP call for every advertising action it can take across Google Ads, Meta Ads, ChatGPT Ads, TikTok Ads, and LinkedIn Ads. Reads run immediately, while writes create a proposal that returns a proposal id and an approval URL, and nothing changes on the ad platform until that proposal is approved. Created campaigns are always paused. The surface includes account discovery, connection health, usage, daily monitors, and platform-specific tools such as creating campaigns, adding keywords and extensions, and reporting on performance. ## For AI agents Manage ad campaigns across Google, Meta, ChatGPT, TikTok, and LinkedIn Ads for AI agents, where writes create a proposal to approve and new campaigns start paused. ## Scope Does not host landing pages, process ad payments, or generate creative assets. Use for managing ad campaigns across connected platforms only. ## Capabilities - Discover and describe the Adako tools available for connected ad accounts - Create paused Google Ads search and Performance Max campaigns for review - Approve or reject pending change proposals before they reach the ad platform - List connected ad accounts and check connection health per platform - Set up daily monitors on an ad account and review the changes they propose - Read performance and plan or task usage for an account ## Use cases ### AI ad-ops agent with human approval An AI agent managing paid search drafts changes but should not push them live on its own. Through Jentic the agent searches for 'create a Google Ads search campaign', loads the matching Adako tool with its input schema, and executes it with the account key injected at call time. The write returns a proposal rather than a live change, so a person approves it before anything reaches the ad platform. Example prompt: Execute POST `/api/v1/tools/google_create_search_campaign/execute` to draft a paused campaign, then list it with POST `/api/v1/tools/list_pending_proposals/execute` for approval ### Cross-platform account health check An agent that oversees several ad platforms reports which accounts are connected and healthy before acting. Adako lists connected accounts and returns connection health per platform, so the agent can flag a broken connection early. It can also read plan and task usage so a batch of changes does not exceed the account's quota. Example prompt: Call POST `/api/v1/tools/list_connected_accounts/execute` and POST `/api/v1/tools/get_usage_status/execute`, then report any unhealthy account ### Daily monitoring and anomaly review A team sets up daily monitors that watch spend and performance and propose corrective changes. Adako creates monitors, lists what each monitor proposed, and lets a reviewer approve or reject those actions. An agent can surface the day's proposed actions and apply only the ones a human confirms. Example prompt: List proposed actions with POST `/api/v1/tools/list_pending_actions/execute` and apply an approved one with POST `/api/v1/tools/manage_action/execute` ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/tools` | List every callable tool | | GET | `/api/v1/tools/{tool_name}` | Describe one tool | | POST | `/api/v1/tools/search_tools/execute` | Find the right tool for a job | | POST | `/api/v1/tools/list_connected_accounts/execute` | List connected ad accounts | | POST | `/api/v1/tools/get_usage_status/execute` | Read plan and task usage | | POST | `/api/v1/tools/google_create_search_campaign/execute` | Create a paused Google Ads search campaign | | POST | `/api/v1/tools/list_pending_proposals/execute` | List proposals waiting for approval | | POST | `/api/v1/tools/approve_proposal/execute` | Approve and execute a pending proposal | ## Key resources - **Tools and discovery** — List and describe every callable tool and search for the right one - **Proposals and accounts** — Approve or reject proposals, list connected accounts, and check connection health - **Platform tools** — Platform-specific operations for Google, Meta, ChatGPT, TikTok, and LinkedIn Ads - **Monitors and reporting** — Daily monitors, proposed actions, usage, and performance reports ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 59 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 97 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 50 / 100 - Agent Usability: 43 / 100 - Security: 60 / 100 - AI Discoverability: 90 / 100 - **View full report:** https://jentic.com/apis/adako.ai/adako/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Adako by hand means issuing an API key, sending it as a bearer token with the right scopes, and handling the proposal-and-approval round trip that every write returns. Through Jentic you install once, import Adako from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Each Adako tool executes at its own path such as `/api/v1/tools/google_create_search_campaign/execute`, so a rule can pin your agent to the specific tools it may run. You choose which it may call, so the proposal-approval tool can stay off the agent's list and keep final sign-off with you. - **Credential handling:** Your Adako API key is stored once, encrypted, by your own Jentic One instance and attached as the bearer token at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a Google Ads campaign' or 'check ad account health', and Jentic returns the matching Adako tool with its input schema so the agent runs the right operation without browsing the full tool list. ## Related APIs - **Criteo API** — Commerce and retargeting ad platform you might run alongside the channels Adako manages - **Outbrain Amplify API** — Native advertising platform for content recommendation campaigns - **Mailchimp Marketing API** — Email marketing and audiences that complement paid acquisition campaigns ## FAQ ### What authentication does the Adako API use? Adako authenticates with a bearer token per its OpenAPI spec: an Adako API key formatted as ak_live_... is sent in the Authorization header, and the key carries scopes such as ads:read and ads:write. Through Jentic the key is held by your own instance and attached per call, so an agent never handles it directly. ### Does the Adako API change my ad campaigns immediately? No. Reads run immediately, but a write creates a proposal that returns a proposal id and an approval URL, and nothing changes on the ad platform until that proposal is approved. Created campaigns are always paused, so an agent can draft changes while a person keeps control of what goes live. ### What are the rate limits for the Adako API? The OpenAPI spec expresses limits as a plan and task quota rather than a fixed request ceiling, and GET `/api/v1/tools/get_usage_status` reports the current usage. Check the Adako documentation for the per-plan task allowance before running large batches of changes. ### Is there an Adako MCP server? You do not need a separate MCP server to use Adako with your agent. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the same ad-management operations on demand without loading another server's tool definitions into its context. ### How do I create a Google Ads campaign through Jentic? Search Jentic for 'create a Google Ads search campaign', load the POST `/api/v1/tools/google_create_search_campaign/execute` operation, and run it with the account and campaign fields. It returns a paused proposal to approve. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the Adako API? Yes. Each tool executes at its own path, so a rule can allow the agent to run only the tools a task needs, such as reading performance and drafting a campaign, while withholding proposal approval so changes still need your sign-off. The agent is bound to the operations you grant, and every call is logged.