Jeeng

Jeeng (formerly PowerInbox, acquired by OpenWeb in 2022 and now marketed as OpenWeb Email Monetization) is a multichannel monetization and audience-engagement platform for digital publishers. It helps publishers grow first-party, opt-in audiences and generate advertising revenue across email newsletters, websites, push notifications, and newsreader apps, reaching more than 150M opt-in subscribers. Its products — AdFill, AdServe, AdMarket, and Renderer — fill vacant ad inventory with monetized content, extend direct ad campaigns into email through existing ad servers, connect advertisers to opt-in audiences, and streamline Google Ad Manager ad-ops workflows. Publisher integration is handled through merge tags, per-newsletter ad tags, and cs_email tracking parameters plus direct Google Ad Manager integration; campaigns and reporting are managed through the portal at manage.jeeng.com. Jeeng also publishes partner Reporting & Management APIs at developers.jeeng.com — an advertiser API for campaign line and creative management plus campaign/performance reporting, and a publisher API for container, placement and publisher performance reporting — served from powerinbox.azure-api.net behind Microsoft Entra ID OAuth 2.0 client-credentials tokens. API access is not self-serve: an account manager provisions the client id and client secret.

Jeeng publishes 3 API contracts indexed on the APIs.io network: Management API, Reporting API, and Revenuestripe.onmicrosoft.com API. Tagged areas include Company, Advertising, Publishing, Email, and Push Notifications.

The Jeeng catalog on APIs.io includes 1 Spectral governance ruleset.

Jeeng’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, authentication, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

44.3/100 developing ▲ 5.2 Agent 33/100 agent ready Front door AI 1/6 silent Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

6 published contracts 1 MCP Servers 3 Agent Skills

Company Advertising Publishing Email Push Notifications Monetization AdTech Newsletters Audience Engagement Reporting Analytics OData OAuth Authentication

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Advertising Sales & Operations Management

BC-3760

ManagementReporting

GET /reporting/advertiserperformance GET /reporting/campaigns/{interval} GET /reporting/publisherperformance POST /management/creative/{id}/transition/{status}

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 44.3/100 · developing

Contract Quality 11.0 / 19

Developer Ergonomics 8.8 / 15

Access Clarity 4.1 / 15

Operational Transparency 0.0 / 10

Contract Governance 1.6 / 9

Discoverability 6.0 / 8

Regulatory Posture 5.1 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 33/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 0 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/jeeng/"><img src="https://apis.io/badge/jeeng/card.svg" alt="Jeeng on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 27.6 — up to +14.5 composite points
Operational Transparency scores 0.0 — up to +13.0 composite points
Contract Quality scores 58.5 — up to +10.4 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/jeeng/apis.yml: open an issue on github.com/api-evangelist/jeeng to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Mobile SDK Publishers (Play SDK Index, CocoaPods, ADA certification)	standard	17.2 (thin)	-	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 5

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OAuth

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OData

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Jeeng Management API

The Management API from Jeeng — 3 operation(s) for management.

Jeeng Reporting API

The Reporting API from Jeeng — 6 operation(s) for reporting.

Jeeng Revenuestripe.onmicrosoft.com API

The Revenuestripe.onmicrosoft.com API from Jeeng — 1 operation(s) for revenuestripe.onmicrosoft.com.

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Jeeng Email Monetization — Advertisers API

OPEN COLLECTION

Jeeng Email Monetization — Authentication (OAuth 2.0 token)

OPEN COLLECTION

Jeeng Email Monetization — Publishers API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Jeeng MCP Server

Jeeng serves an MCP endpoint at https://developers.jeeng.com/mcp. It is the documentation MCP that ships with the ReadMe developer hub — it exposes the docs corpus to an agent, ...

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

jeeng-manage-a-campaign-line

AGENT SKILL

jeeng-pull-a-publisher-inventory-report

AGENT SKILL

jeeng-pull-an-advertiser-campaign-report

AGENT SKILL

Jeeng API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Jeeng Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Jeeng Rate Limits

0 limits

RATE LIMITS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Jeeng API Rules

52 rules · 48 errors 3 warnings 1 info

SPECTRAL

OpenAPI Overlays 3

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Jeeng Advertisers Overlay

4 actions · documentation · jeeng-advertisers.json

DERIVED

Jeeng Authentication Overlay

3 actions · documentation · jeeng-authentication.json

DERIVED

Jeeng Publishers Overlay

4 actions · documentation · jeeng-publishers.json

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Jeeng Authentication

oauth2 · 1 scheme

SECURITY

Jeeng Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Jeeng Scopes

1 scope · client_credentials

1 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

MCPServer

MCPServer

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Build 2

SDKs, sample code, and the tooling you integrate with

Packages

Packages

ToolCrosswalk

ToolCrosswalk

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 5

Properties that don't map to a standard resource type

ParentCompany

CapabilityMap

Overlay

Overlay

Overlay

Source (apis.yml)

aid: jeeng
name: Jeeng
description: 'Jeeng (formerly PowerInbox, acquired by OpenWeb in 2022 and now marketed as OpenWeb Email Monetization) is a
  multichannel monetization and audience-engagement platform for digital publishers. It helps publishers grow first-party,
  opt-in audiences and generate advertising revenue across email newsletters, websites, push notifications, and newsreader
  apps, reaching more than 150M opt-in subscribers. Its products — AdFill, AdServe, AdMarket, and Renderer — fill vacant ad
  inventory with monetized content, extend direct ad campaigns into email through existing ad servers, connect advertisers
  to opt-in audiences, and streamline Google Ad Manager ad-ops workflows. Publisher integration is handled through merge tags,
  per-newsletter ad tags, and cs_email tracking parameters plus direct Google Ad Manager integration; campaigns and reporting
  are managed through the portal at manage.jeeng.com. Jeeng also publishes partner Reporting & Management APIs at developers.jeeng.com
  — an advertiser API for campaign line and creative management plus campaign/performance reporting, and a publisher API for
  container, placement and publisher performance reporting — served from powerinbox.azure-api.net behind Microsoft Entra ID
  OAuth 2.0 client-credentials tokens. API access is not self-serve: an account manager provisions the client id and client
  secret.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: sales
  trial: false
  try_now: false
  public: false
  label: Sales-gated partner API
  confidence: high
  source:
  - https://developers.jeeng.com/docs/publisher-overview
  - https://developers.jeeng.com/docs/advertiser-overview
  generated: '2026-08-12'
  method: searched
image: https://www.jeeng.com/wp-content/uploads/2022/04/Jeeng_w_OW.png
url: https://raw.githubusercontent.com/api-evangelist/jeeng/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
- battery-ventures
x-tier: enriched
x-tier-reason: enrichment-pipeline
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-12'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-03
tags:
- Company
- Advertising
- Publishing
- Email
- Push Notifications
- Monetization
- AdTech
- Newsletters
- Audience Engagement
- Reporting
- Analytics
- OData
- OAuth
- Authentication
tags_raw:
- Company
- Advertising
- Publishing
- Email
- Push Notifications
- Monetization
- AdTech
- Newsletters
- Audience Engagement
- Reporting
- Analytics
- OData
- OAuth
- Authentication
apis:
- aid: jeeng:jeeng-management-api
  name: Jeeng Management API
  description: The Management API from Jeeng — 3 operation(s) for management.
  humanURL: https://developers.jeeng.com/reference
  baseURL: https://powerinbox.azure-api.net/
  tags:
  - Management
  properties:
  - type: OpenAPI
    url: openapi/jeeng-management-api-openapi.yml
  - type: Documentation
    url: https://developers.jeeng.com/docs/advertiser-overview
  - type: APIReference
    url: https://developers.jeeng.com/reference
  - type: Documentation
    url: https://developers.jeeng.com/docs/publisher-overview
  - type: Documentation
    url: https://developers.jeeng.com/reference/getting-an-access-token
  - type: APIReference
    url: https://developers.jeeng.com/reference/getting-an-access-token
- aid: jeeng:jeeng-reporting-api
  name: Jeeng Reporting API
  description: The Reporting API from Jeeng — 6 operation(s) for reporting.
  humanURL: https://developers.jeeng.com/reference
  baseURL: https://powerinbox.azure-api.net/
  tags:
  - Reporting
  properties:
  - type: OpenAPI
    url: openapi/jeeng-reporting-api-openapi.yml
  - type: Documentation
    url: https://developers.jeeng.com/docs/advertiser-overview
  - type: APIReference
    url: https://developers.jeeng.com/reference
  - type: Documentation
    url: https://developers.jeeng.com/docs/publisher-overview
  - type: Documentation
    url: https://developers.jeeng.com/reference/getting-an-access-token
  - type: APIReference
    url: https://developers.jeeng.com/reference/getting-an-access-token
- aid: jeeng:jeeng-revenuestripe-onmicrosoft-com-api
  name: Jeeng Revenuestripe.onmicrosoft.com API
  description: The Revenuestripe.onmicrosoft.com API from Jeeng — 1 operation(s) for revenuestripe.onmicrosoft.com.
  humanURL: https://developers.jeeng.com/reference
  baseURL: https://powerinbox.azure-api.net/
  tags:
  - Revenuestripe.onmicrosoft.com
  properties:
  - type: OpenAPI
    url: openapi/jeeng-revenuestripe-onmicrosoft-com-api-openapi.yml
  - type: Documentation
    url: https://developers.jeeng.com/docs/advertiser-overview
  - type: APIReference
    url: https://developers.jeeng.com/reference
  - type: Documentation
    url: https://developers.jeeng.com/docs/publisher-overview
  - type: Documentation
    url: https://developers.jeeng.com/reference/getting-an-access-token
  - type: APIReference
    url: https://developers.jeeng.com/reference/getting-an-access-token
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: ParentCompany
  url: https://apis.io/providers/openweb/
  name: OpenWeb
  x-relationship: acquired
  x-evidence: Jeeng (formerly PowerInbox, acquired by OpenWeb in 2022 and now marketed as OpenWeb Email Monetization) is a
    multichannel monetization and audience-engagement platform for digital publishers.
- type: CapabilityMap
  url: capabilities/jeeng-capability-edges.yml
  name: Jeeng Business Capability Map
- type: Overlay
  url: overlays/jeeng-advertisers-overlay.yaml
- type: Overlay
  url: overlays/jeeng-publishers-overlay.yaml
- type: Overlay
  url: overlays/jeeng-authentication-overlay.yaml
- type: Website
  url: https://jeeng.com
- type: DeveloperPortal
  url: https://developers.jeeng.com/
- type: Documentation
  url: https://developers.jeeng.com/docs/getting-started
- type: APIReference
  url: https://developers.jeeng.com/reference
- type: GettingStarted
  url: https://developers.jeeng.com/docs/getting-started
- type: TermsOfService
  url: https://www.jeeng.com/terms-of-use/
- type: PrivacyPolicy
  url: https://www.jeeng.com/privacy-policy/
- type: Support
  url: https://www.jeeng.com/contact-us/
- type: Blog
  url: https://www.jeeng.com/news/
- type: Login
  url: https://manage.jeeng.com/
- type: DomainSecurity
  url: security/jeeng-domain-security.yml
- type: LLMsTxt
  url: llms/jeeng-llms.txt
- type: Authentication
  url: authentication/jeeng-authentication.yml
- type: OAuthScopes
  url: scopes/jeeng-scopes.yml
- type: Conventions
  url: conventions/jeeng-conventions.yml
- type: ErrorCatalog
  url: errors/jeeng-problem-types.yml
- type: Lifecycle
  url: lifecycle/jeeng-lifecycle.yml
- type: Conformance
  url: conformance/jeeng-conformance.yml
- type: DataModel
  url: data-model/jeeng-data-model.yml
- type: Packages
  url: packages/jeeng-packages.yml
- type: Plans
  url: plans/jeeng-plans-pricing.yml
- type: RateLimits
  url: rate-limits/jeeng-rate-limits.yml
- type: MCPServer
  url: mcp/jeeng-mcp.yml
- type: ToolCrosswalk
  url: mcp/jeeng-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 26
  pass: local-v1
  note: Round 1 recorded "Jeeng publishes no public developer API". That was wrong. STEP 0b contract discovery found a live
    ReadMe developer hub at developers.jeeng.com (readme-subdomain "jeeng") publishing three OpenAPI 3.1.0 definitions and
    ten operations against https://powerinbox.azure-api.net/, plus a served llms.txt and a gated MCP endpoint.

Jeeng API — frequently asked questions

Does Jeeng have an API?

Yes. APIs.io lists 3 APIs from Jeeng, including Jeeng Management API, Jeeng Reporting API and Jeeng Revenuestripe.onmicrosoft.com API.

Is there an OpenAPI specification for the Jeeng API?

Yes. APIs.io indexes 3 OpenAPI specifications for Jeeng, each linked for download from this page.

How do I authenticate with the Jeeng API?

Jeeng uses bearer-token authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Jeeng Authentication.

Does Jeeng have an MCP server?

Yes. APIs.io lists 1 MCP server for Jeeng: Jeeng serves an MCP endpoint at https://developers.jeeng.com/mcp. It is the documentation MCP that ships with the ReadMe developer hub — it exposes the docs corpus to an agent, NOT the advertiser and

Is the Jeeng API ready for AI agents?

Jeeng has a Kin Score of 44.3 out of 100 (developing) and an Agent Readiness score of 32.6 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/jeeng"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/jeeng/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/jeeng/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.