Install Jentic One Beta

Connect the NPR Sponsorship Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NPR Sponsorship Service, 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%2Fnpr.org%2Fsponsorship" | 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%2Fnpr.org%2Fsponsorship" | 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 NPR Sponsorship Service API.

Fetch the next sponsor audio spot to play in an NPR-licensed audio app

Retrieve impression-tracking pixels for sponsor delivery reporting

Surface sponsor metadata including duration and creative asset URL

Honor NPR's sponsorship rotation rules through the service's scheduling logic

Issue impression callbacks back to NPR for accurate spot attribution

GET STARTED

Start building with NPR Sponsorship Service API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use NPR Sponsorship Service API for, with concrete tasks.

★ Sponsor Insertion in Third-Party NPR Audio Apps

Apps licensed to play NPR audio outside of NPR One must request sponsor spots from the Sponsorship Service before playing each segment. The /v2/ads endpoint returns the audio creative URL and impression tracking pixels, ensuring sponsorship inventory is delivered and counted correctly. Without this call, the app cannot legally play NPR content under its licensing terms.

Call GET /v2/ads with the required client identifiers and play the returned creative URL before resuming NPR audio

Impression Reporting for Sponsorship Compliance

Sponsorship revenue depends on accurate impression counts. The Sponsorship Service returns tracking pixels with each spot, and clients must fire those pixels at playback start to report delivery. This use case covers the reporting half of the contract - without firing tracking, NPR cannot bill sponsors accurately.

Parse the impression tracking URLs from the /v2/ads response and issue HTTP GETs against each one at playback start

AI Agent Audio App Integration via Jentic

AI agents that orchestrate audio playback for partner apps use Jentic to discover and call the Sponsorship Service alongside the Station Finder. Through Jentic, the agent can request a sponsor spot, fire impression callbacks, and resume NPR content without holding NPR OAuth secrets in its prompt context.

Use Jentic to search for 'fetch NPR sponsor spot', load the /v2/ads schema, and execute it before starting NPR audio playback

Key Endpoints

2 endpoints — the npr sponsorship service returns sponsor advertisement payloads for non-npr one client applications that play npr audio.

METHOD

PATH

DESCRIPTION

GET

/v2/ads

Fetch the next NPR sponsor spot with tracking pixels

GET

/v2/ads

Fetch the next NPR sponsor spot with tracking pixels

Why Jentic?

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

Setup

Wiring the NPR Sponsorship Service by hand means carrying OAuth 2.0 credentials into calls to sponsorship.api.npr.org and handling sponsor-spot retrieval and tracking yourself. Through Jentic you install once, import the NPR Sponsorship Service from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The sponsor-spot target here travels in the request rather than a URL path resource, so scope the agent to the operations it needs. This service exposes a single read operation, so the agent retrieves sponsor spots and nothing more unless you add other operations.

Credential isolation

Your NPR OAuth client credentials for the sponsorship service are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'fetch an NPR sponsor spot', and Jentic returns the GET /v2/ads operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using NPR Sponsorship Service API through Jentic.

What authentication does the NPR Sponsorship Service use?

The NPR Sponsorship Service uses OAuth 2.0 authorization code flow with the NPR identity authorization server at https://authorization.api.npr.org/v2/token. Through Jentic, NPR OAuth client credentials are isolated in the vault and only short-lived tokens reach the agent's request context.

Can I fetch a sponsor spot to play before NPR audio with this API?

Yes. GET /v2/ads returns the next sponsor creative with its audio asset URL, duration, and impression tracking pixels for your client to fire at playback.

What are the rate limits for the NPR Sponsorship Service?

NPR does not publish a numeric rate limit for /v2/ads, but the service is intended to be called once per audio segment boundary. Calling it more aggressively risks rotation logic returning the same spot.

How do I insert an NPR sponsor spot through Jentic?

Search Jentic for 'fetch NPR sponsor spot', load the /v2/ads schema, and execute. The flow is: pip install jentic, then await client.search, load, and execute against https://sponsorship.api.npr.org.

Is the NPR Sponsorship Service free to use?

The API itself has no usage fee, but access requires an NPR One Enterprise licensing agreement, including sponsor-insertion compliance terms documented at https://dev.npr.org/guide/app-experience/sponsorship/.

Can I limit what my agent is allowed to do with the NPR Sponsorship API?

Yes. Because Jentic One is self-hosted, you decide which operations and credentials your agent may use, and your own rules govern what it can call. This service exposes a single read operation, GET /v2/ads, so you can scope the agent to just fetching the next sponsor spot and its impression-tracking pixels, and nothing more unless you grant additional operations. Your NPR OAuth client credentials stay on your instance and are injected only at execution time, so the agent never holds them.

NPR Sponsorship Service

Browse all Npr APIs

AI ReadinessAI-Aware (A-)73/100

See full scorecard

Community OpenAPI document · agent-readyMediaAudio Processingoauth22 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Fetch NPR sponsorship audio spots and impression-tracking metadata for insertion between NPR audio segments. One core endpoint at /v2/ads.

Use for: Fetch the next NPR sponsor spot to play, Retrieve a sponsorship audio asset URL for insertion, Get tracking pixels for an NPR sponsor impression, Check what sponsor message should play after a news segment

Not supported: Does not handle audio playback, station lookup, or general advertising inventory - use for NPR-licensed sponsorship spot retrieval and tracking only.

The NPR Sponsorship Service returns sponsor advertisement payloads for non-NPR One client applications that play NPR audio. Clients call the /v2/ads endpoint to fetch the next sponsorship spot to play, including the audio asset URL and tracking pixels for impression reporting. The service is OAuth 2.0 protected and is designed to be called between NPR audio segments to insert sponsor content compliantly.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

21%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

47%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

67%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

90%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the NPR Sponsorship Service to your agent

Capabilities

Start building with NPR Sponsorship Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

NPR Sponsorship Service

Jentic AI Readiness Score

NPR Sponsorship Service

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness