Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Meta Marketing API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgraph.facebook.com%2Fmeta-marketing" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgraph.facebook.com%2Fmeta-marketing" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Meta Marketing API.
Create and list ad campaigns under an ad account
Define ad sets with targeting and budget inside a campaign
Build ads from ad creatives for an ad account
Create custom audiences for ad targeting
Read performance insights at the account, campaign, ad set, and ad level
GET STARTED
Delete campaigns, ad sets, or ads from an ad account
Patterns agents use Meta Marketing API for, with concrete tasks.
★ Agent-Driven Campaign Launch
An AI agent connected through Jentic launches a Meta ad by creating a campaign, adding an ad set with targeting and budget, and attaching an ad built from a creative. Because the objects nest from campaign to ad set to ad under one ad account, the agent assembles a complete, structured campaign without clicking through Ads Manager.
Create a campaign, add an ad set with targeting and a daily budget, then create an ad from a creative under the ad account
Ad Performance Reporting
Reporting tools pull spend and results with the insights endpoints, which return performance at the account, campaign, ad set, and ad level. An agent requests insights for a campaign to refresh a dashboard rather than aggregating raw delivery events.
Request insights for a campaign over the last 7 days and summarize spend, impressions, and results
Audience Building and Retargeting
Growth teams create custom audiences for targeting and retargeting across Meta's placements. The custom-audiences endpoint under an ad account lets an agent create and list audiences, so a workflow prepares targeting before an ad set references it.
Create a custom audience for an ad account and confirm it is available for ad set targeting
64 endpoints — the meta marketing api creates and manages paid advertising on facebook, instagram, messenger, and the audience network.
METHOD
PATH
DESCRIPTION
/act_{ad_account_id}/campaigns
Create an ad campaign
/act_{ad_account_id}/campaigns
List ad campaigns
/act_{ad_account_id}/adsets
Create an ad set with targeting and budget
/act_{ad_account_id}/ads
Create an ad
/act_{ad_account_id}/adcreatives
Create an ad creative
/act_{ad_account_id}/customaudiences
Create a custom audience
/act_{ad_account_id}/insights
Read ad account performance insights
/act_{ad_account_id}/campaigns
Create an ad campaign
/act_{ad_account_id}/campaigns
List ad campaigns
/act_{ad_account_id}/adsets
Create an ad set with targeting and budget
/act_{ad_account_id}/ads
Create an ad
/act_{ad_account_id}/adcreatives
Create an ad creative
/act_{ad_account_id}/customaudiences
Create a custom audience
/act_{ad_account_id}/insights
Read ad account performance insights
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Meta Marketing API by hand means running the Facebook OAuth 2.0 authorization-code flow, requesting the right ad scopes, and refreshing tokens yourself. Through Jentic you install once, import the Meta Marketing API from the API Directory, store the token once, and your agent calls the campaign, audience, and insights operations.
Permission scoping
The ad account id sits in the URL path as act_{ad_account_id}, so a rule can pin your agent to one ad account. You choose the operations it may call, so destructive ones like campaign deletion are not included unless you add them.
Credential isolation
Your Meta access token is held by your own Jentic One instance, encrypted, and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a Meta ad campaign' or 'read campaign insights', and Jentic returns the matching Meta Marketing operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Meta Marketing API through Jentic.
What authentication does the Meta Marketing API use?
The API uses Facebook OAuth 2.0 access tokens via the authorization-code flow, with scopes such as `ads_management`, `ads_read`, `business_management`, and `pages_read_engagement` as declared in its OpenAPI spec. Through Jentic the token is held by your own Jentic One instance and attached to each request at execution time, so it never appears in your agent's prompt or logs.
Can I create ad campaigns with the Meta Marketing API?
Yes. You create a campaign under an ad account, add ad sets that carry targeting and budget, and attach ads built from ad creatives. Because the objects nest from campaign to ad set to ad, your agent assembles a complete campaign structure in a few calls.
What are the rate limits for the Meta Marketing API?
The OpenAPI spec does not specify rate limits; Meta applies account-level ads throttling that varies by spend and access tier. Check the Meta Marketing API documentation at https://developers.facebook.com/docs/marketing-apis/ for current limits before running bulk campaign jobs.
Is there a Meta Marketing API MCP server?
You do not need an MCP server to give your agent the Meta Marketing API. Jentic connects it directly from the API Directory: import it, store your access token once, and your agent calls the campaign, audience, and insights operations on demand without loading an extra server's tool definitions into its context.
Can I limit what my agent is allowed to do with the Meta Marketing API?
Yes. The ad account id sits in the URL path as `act_{ad_account_id}`, so write a rule that allows only the campaign and insights read operations under one ad account id. The agent can then review that account's campaigns and performance and touch nothing else, and every call it makes is logged.
How do I launch a Meta ad campaign through Jentic?
Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the Meta Marketing API from the Jentic directory and search by intent such as 'create a Meta ad campaign'. Jentic returns the matching operation with its input schema so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Create and manage Meta ad campaigns, ad sets, ads, and creatives for an ad account, build custom audiences, and read performance insights across Facebook, Instagram, Messenger, and the Audience Network.
Use for: Create a new ad campaign under my Meta ad account, Set up an ad set with targeting and a daily budget, Build an ad from an existing ad creative, Get the performance insights for a campaign
Not supported: Does not handle organic page posting, direct messaging, or payment processing. Use for managing paid Meta ad campaigns, audiences, and reporting only.
The Meta Marketing API creates and manages paid advertising on Facebook, Instagram, Messenger, and the Audience Network. An ad account holds campaigns, which contain ad sets that define targeting and budget, which in turn contain ads built from ad creatives. Custom audiences are defined for targeting, and insights endpoints return performance data at the account, campaign, ad set, and ad level.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>