Anura Reporting API

Name: Anura Reporting API
Brand: Anura Reporting API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsWeb AnalyticsapiKey11 EndpointsREST

For Agents

Pull ad-fraud session, browser, geography, and network reports from Anura across Direct, Script, and Interface modes. Suited to dashboard, alerting, and review agents that surface fraud signals.

Install Jentic One Beta

Connect the Anura Reporting API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Anura Reporting 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Anura Reporting API.

Pull session-count breakdowns by Direct, Script, and Interface integration modes for a date window

Read browser distribution reports to spot anomalous user-agent concentrations

Retrieve geography reports showing session counts and fraud rates by country or region

GET STARTED

Start building with Anura Reporting API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Anura Reporting API for, with concrete tasks.

★ Daily Fraud Review Dashboard

Build a daily dashboard that pulls session, geography, and network reports for the past 7 days from POST /script/sessions, /script/geography, and /script/networks and renders fraud-rate trends per source. Anura returns counts split by suspicious, warning, and good classifications, so the dashboard can highlight the campaigns or geos driving the day's fraud spike without exposing raw event-level data.

Call POST /script/sessions, /script/geography, and /script/networks for the last 7 days, then aggregate the suspicious counts per source for the dashboard

Campaign-Level Fraud Alerting

Watch a campaign by polling POST /interface/campaigns alongside the Interface session and network endpoints, raising an alert when the suspicious rate exceeds a threshold. Because Anura caps date-specific queries at a 7-day rolling window (31 days for Overview), the agent runs short, frequent polls rather than long historical pulls - which suits a streaming alert pipeline.

Call POST /interface/campaigns to list active campaigns, then for each call POST /script/sessions for the last hour and trigger an alert if the suspicious rate exceeds 5 percent

Source and Instance Inventory

Maintain a configuration catalogue of every Anura instance, source, and campaign by listing them via POST /interface/instances, /interface/sources, and /interface/campaigns. The agent uses this to validate that a downstream system's source IDs match Anura's records and to scope subsequent Direct or Script reporting calls without hard-coding identifiers.

Call POST /interface/instances, then POST /interface/sources and /interface/campaigns and persist the returned IDs as the canonical configuration list

AI Agent Fraud Reporting via Jentic

An AI agent that triages ad-fraud incidents can pull Anura reports through Jentic without managing the token query parameter directly. Jentic's intent search routes the agent to the right /script, /direct, or /interface endpoint with its parameter schema, and the token is loaded from the vault at execution time so it never enters the agent's tool context.

Search Jentic for 'pull Anura session report for last 7 days', load POST /script/sessions, and execute with the Script source ID and date window

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for anura reporting api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/script/sessions

Session-count report for the Script integration

POST

/script/geography

Geography breakdown for the Script integration

POST

/script/networks

Network breakdown for the Script integration

POST

/script/browsers

Browser breakdown for the Script integration

POST

/direct/sessions

Session-count report for the Direct integration

POST

/interface/instances

List configured Anura instances

POST

/interface/sources

List configured sources

POST

/interface/campaigns

List configured campaigns

POST

/script/sessions

Session-count report for the Script integration

POST

/script/geography

Geography breakdown for the Script integration

POST

/script/networks

Network breakdown for the Script integration

POST

/script/browsers

Browser breakdown for the Script integration

POST

/direct/sessions

Session-count report for the Direct integration

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Anura token is stored once, encrypted, by your own Jentic One instance 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 'pull the session report for the last 7 days' or 'get a geography breakdown', and Jentic returns the matching Anura operation with its input schema so the agent calls the right endpoint without mapping between Script, Direct, and Interface modes from the reference docs.

Time to first call

FAQs

Specific to using Anura Reporting API through Jentic.

Why is there no official OpenAPI spec for Anura Reporting API?

Anura publishes its reporting docs at docs.anura.io as HTML reference rather than a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Anura via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Anura Reporting API use?

Anura uses an API token sent as a query parameter named token on every request. Through Jentic the token is stored in the encrypted vault and injected at execution time, so the raw token never enters the agent's prompt context.

Can I pull session reports for arbitrary date ranges from Anura?

No. Date-specific reports are limited to a 7-day rolling time frame, except Overview endpoints which extend to 31 days. Schedule daily or hourly poll jobs that stay inside the rolling window rather than requesting long historical ranges.

What are the rate limits for the Anura Reporting API?

The OpenAPI spec does not declare explicit rate limits. Anura caps every report to a 7-day window (31 days for Overview) which naturally bounds traffic, but you should still back off on 429 responses and avoid running every endpoint in parallel for every source.

How do I pull a daily session report from Anura through Jentic?

Run pip install jentic, then search Jentic for 'pull Anura session report for last 7 days'. Jentic returns POST /script/sessions with its filter schema. Execute with your Script source ID and the desired date range; the token is injected from the vault.

Why are all Anura endpoints POST instead of GET?

Anura models report parameters (date range, source, instance, classification filters) as a JSON body rather than query strings, so every reporting endpoint uses POST. Only the token authentication value is sent as a query parameter.

Can I limit what my agent is allowed to do with the Anura Reporting API?

Yes. Because Jentic One is self-hosted, your own rules decide which Anura operations and credentials the agent can use. Every Anura operation here is a read-only report, and the token and report filters travel in the request body rather than a path id, so you scope the agent to only the reports it needs, such as the session and geography endpoints, while withholding the network, browser, or Interface listing calls. The agent can never reach an operation you have not granted it.

Anura Reporting API

Connect the Anura Reporting API to your agent

Capabilities

Start building with Anura Reporting API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs