Install Jentic One Beta

Connect the Native Ads Publisher API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Native Ads Publisher 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%2Fnativeads.com%2Fnative-ads-publisher-api" | sh

Step 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%2Fnativeads.com%2Fnative-ads-publisher-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Native Ads Publisher API.

Authenticate and obtain a publisher token through the login operation

Retrieve daily publisher performance reports over a date range

Retrieve per-website publisher reports over a date range

Retrieve per-widget publisher reports over a date range

Use Cases

Patterns agents use Native Ads Publisher API for, with concrete tasks.

GET STARTED

Start building with Native Ads Publisher API

Explore with Jentic One

View OpenAPI Document

★ Daily Revenue Reporting Inside an AI Agent

An AI agent logs in for a token and then pulls the daily publisher report for a date range, paging through the results. The daily report operation returns earnings and activity per day, so a monitoring assistant can summarize how a publisher account is performing without opening the account interface.

Call the login operation for a token, then request the daily report with a start and end date and page through the results.

Website-Level Performance Breakdown

A workflow compares how different websites in a publisher account are earning. The website report operation returns activity grouped by website over a date range, giving an agent the figures it needs to rank sites or flag drops.

Request the website report with the token and a date range, then compare the per-website figures.

Widget Performance Monitoring

An agent tracks how individual ad widgets perform so it can spot which placements earn most. The widget report operation returns activity grouped by widget over a date range, letting the agent monitor placements on a schedule.

Request the widget report with the token and a date range, then track the per-widget figures over time.

Key Endpoints

4 endpoints — the native ads publisher api returns publisher performance reports for a native ads account, matching the functionality of the publisher account interface.

METHOD

PATH

DESCRIPTION

POST

/auth/default/login

GET

/publisher/reports/daily

Retrieve daily publisher reports

GET

/publisher/reports/website

Retrieve per-website publisher reports

GET

/publisher/reports/widget

Retrieve per-widget publisher reports

POST

/auth/default/login

GET

/publisher/reports/daily

Retrieve daily publisher reports

GET

/publisher/reports/website

Retrieve per-website publisher reports

GET

/publisher/reports/widget

Retrieve per-widget publisher reports

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Native Ads Publisher API by hand means logging in to fetch a token, appending it to every report call, and paging through date-ranged results yourself. Through Jentic you install once, import it from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The operations are what a rule bounds, so you can allow just the daily report and leave the website and widget reports out. You choose the operations your agent may call, so the rest are not included unless you add them.

Credential isolation

Your Native Ads Publisher credentials are stored once, encrypted, by your own Jentic One instance, and the token is injected as the token query parameter at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get a native ads publisher report' or 'ad revenue by website', and Jentic returns the matching Native Ads operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Native Ads Publisher API through Jentic.

What authentication does the Native Ads Publisher API use?

The three report operations require a token passed as the token query parameter, per its OpenAPI spec. You obtain that token from the login operation, which itself needs no token. Through Jentic the credentials are stored encrypted in your own Jentic One instance and injected at call time.

What reports can the Native Ads Publisher API return?

It returns daily, per-website, and per-widget publisher reports. Each takes a start date, an end date, and limit and page parameters, so an agent can request a date range and page through the results.

What are the rate limits for the Native Ads Publisher API?

The OpenAPI spec does not specify rate limits. Each report call takes limit and page parameters, so an agent pages through results; check the Native Ads documentation for any account limits.

How do I pull a native ads report through Jentic?

Search Jentic for 'get a native ads publisher report', add the Native Ads Publisher API from the directory, and your agent logs in for a token, then calls the daily, website, or widget report with a start and end date. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Native Ads Publisher API MCP server?

You don't need an MCP server to give your agent the Native Ads Publisher API. Jentic connects it directly from the API Directory: import it, store your login credentials once, and your agent calls the report operations. Nothing extra loads into the agent's context until a call is made.

Can I limit what my agent is allowed to do with the Native Ads Publisher API?

Yes. Write a rule that allows just the operations you want, such as the daily report without the website or widget reports, so the agent cannot call anything else, and every call is logged. The API takes its inputs as query parameters, so rules bound which operations your agent may call.

Native Ads Publisher API

Name: Native Ads Publisher API
Brand: Native Ads Publisher API
Availability: InStock

Community OpenAPI document · agent-readyMarketingAdvertisingapikey4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Log in for an authentication token, then pull publisher performance reports by day, by website, and by widget over a date range for a Native Ads account.

Use for: Log in to get my publisher token, Pull my daily native ads report, Show revenue by website this month, Break down performance by widget

Not supported: Does not handle campaign creation, billing, or ad serving. Use for retrieving publisher performance reports only.

The Native Ads Publisher API returns publisher performance reports for a Native Ads account, matching the functionality of the publisher account interface. It reports earnings and activity by day, by website, and by widget over a date range, and issues the authentication token those report calls require through a login operation.

Jentic One on Github View OpenAPI Document