LoopMe

LoopMe is a global brand-performance advertising platform that uses AI to bring brands into mobile and CTV apps. Its products span an AI-powered intelligent marketplace, PurchaseLoop outcome-based brand advertising, the Chartboost in-app monetization platform, and an Audience & Measurement Platform (AMP). For developers, LoopMe exposes a REST Reporting API for publisher (app/site) and advertiser (campaign) statistics, a server-to-server (S2S) ad request API, first-party United SDKs for Android and iOS, and a Prebid.js header-bidding adapter. LoopMe is backed by HV Capital and headquartered in the UK.

LoopMe publishes 3 API contracts indexed on the APIs.io network: S2S Ad Serving API, Advertiser Reporting API, and Publisher Reporting API. Tagged areas include Company, Advertising, AdTech, Mobile Advertising, and CTV.

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

LoopMe’s developer surface includes documentation, API reference, engineering blog, support, authentication, changelog, sandbox, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

39.9/100 developing ▬ flat Agent 34/100 agent ready Heartbeat 98/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 published contracts 2 Agent Skills

Company Advertising AdTech Mobile Advertising CTV Reporting Programmatic Ai Enterprise Software SDK

Kin Score

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

Composite quality — 39.9/100 · developing

Contract Quality 2.8 / 21

Developer Ergonomics 10.4 / 17

Access Clarity 7.4 / 17

Operational Transparency 2.0 / 11

Contract Governance 3.2 / 10

Discoverability 6.2 / 9

Regulatory Posture 4.4 / 15

Agent readiness — 34/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 4 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 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 3 / 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 does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/loopme/"><img src="https://apis.io/badge/loopme/card.svg" alt="LoopMe 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
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

3 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 13.2 — up to +21.7 composite points
Access Clarity scores 43.4 — up to +11.3 composite points
Operational Transparency scores 18.4 — up to +10.6 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/loopme/apis.yml: open an issue on github.com/api-evangelist/loopme 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	20.4 (thin)	-	-
TAG-Certified Ad Fraud and Brand Safety	standard	20.4 (thin)	-	-

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 1

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 3

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

LoopMe S2S Ad Serving API

LoopMe's server-to-server ad request endpoint. A third-party ad server, exchange or mediation platform sends a GET describing the device, app and user, and LoopMe returns an MRA...

LoopMe Advertiser Reporting API

The Advertiser Reporting API from LoopMe — 1 operation(s) for advertiser reporting.

LoopMe Publisher Reporting API

The Publisher Reporting API from LoopMe — 1 operation(s) for publisher reporting.

Open Collections 3

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

LoopMe S2S Ad Request API

OPEN COLLECTION

LoopMe Reporting Ad Serving Advertiser Reporting API

OPEN COLLECTION

LoopMe Reporting Ad Serving Publisher Reporting API

OPEN COLLECTION

Agent Skills 2

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

Pull LoopMe reporting statistics

AGENT SKILL

Request a LoopMe ad server-to-server

AGENT SKILL

LoopMe API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Loopme Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Loopme Rate Limits

0 limits

RATE LIMITS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

LoopMe API Rules

55 rules · 53 errors 1 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.

Loopme Ad Serving Api Overlay

3 actions · documentation · loopme-ad-serving-api-openapi.yml

DERIVED

Loopme Advertiser Reporting Api Overlay

3 actions · documentation · loopme-advertiser-reporting-api-openapi.yml

DERIVED

Loopme Publisher Reporting Api Overlay

3 actions · documentation · loopme-publisher-reporting-api-openapi.yml

DERIVED

Security Posture 3

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

Loopme Authentication

apiKey · 1 scheme

SECURITY

Loopme Domain Security

TLSv1.3 · DMARC

SECURITY

Loopme Trust Center

ePrivacyseal, TAG registered (Trustworthy Accountability Group)

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Loopme Agentic Access

3 operations

3 operations · 0 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Sandbox

Sandbox

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Lifecycle

DataModel

Conformance

Components

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

SDKs

SDKs

Packages

Packages

Access & Security 4

Authentication, authorization, and security posture

Authentication

DomainSecurity

Compliance

TrustCenter

Operate 3

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Plans

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: loopme
name: LoopMe
description: LoopMe is a global brand-performance advertising platform that uses AI to bring brands into mobile and CTV apps.
  Its products span an AI-powered intelligent marketplace, PurchaseLoop outcome-based brand advertising, the Chartboost in-app
  monetization platform, and an Audience & Measurement Platform (AMP). For developers, LoopMe exposes a REST Reporting API
  for publisher (app/site) and advertiser (campaign) statistics, a server-to-server (S2S) ad request API, first-party United
  SDKs for Android and iOS, and a Prebid.js header-bidding adapter. LoopMe is backed by HV Capital and headquartered in the
  UK.
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: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://loopme.ai/wp-content/themes/loopme/assets/images/logo.svg
url: https://raw.githubusercontent.com/api-evangelist/loopme/refs/heads/main/apis.yml
humanURL: https://loopme.ai/
x-type: company
x-source: vc-portfolio
x-backed-by:
- hv-capital
x-tier: profiled
x-tier-reason: enriched-from-public-developer-surface
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-09-16'
x-docs-platform: nextra
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
x-docs-hosting: vercel
tags:
- Company
- Advertising
- AdTech
- Mobile Advertising
- CTV
- Reporting
- Programmatic
- Ai Enterprise Software
- SDK
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: loopme:loopme-ad-serving-api
  name: LoopMe S2S Ad Serving API
  description: LoopMe's server-to-server ad request endpoint. A third-party ad server, exchange or mediation platform sends
    a GET describing the device, app and user, and LoopMe returns an MRAID ad payload (ad HTML plus impression and click beacon
    URLs), an empty ads array when there is no fill, or an HTTP 404 error envelope. Identified by the appId LoopMe provisions
    to the publisher rather than by a token.
  humanURL: https://wiki.loopme.cool/publishers/integrations/s2s
  baseURL: https://loopme.me/api/s2s
  x-base-url-note: Corrected 2026-08-13. The tag-split refine pass had assigned this ad-serving operation the Reporting API
    base (https://reports.loopme.com/api/v1); the S2S reference documents https://loopme.me/api/s2s/ads, which matches openapi/_original/loopme-s2s-openapi.yml.
  tags:
  - Ad Serving
  properties:
  - type: OpenAPI
    url: openapi/loopme-ad-serving-api-openapi.yml
  - type: Overlay
    url: overlays/loopme-ad-serving-api-overlay.yaml
  - type: AgentSkill
    url: skills/loopme-request-ad-s2s.md
  - type: Documentation
    url: https://wiki.loopme.cool/publishers/integrations/s2s
- aid: loopme:loopme-advertiser-reporting-api
  name: LoopMe Advertiser Reporting API
  description: The Advertiser Reporting API from LoopMe — 1 operation(s) for advertiser reporting.
  humanURL: https://wiki.loopme.cool/publishers/reporting-api
  baseURL: https://reports.loopme.com/api/v1
  tags:
  - Advertiser Reporting
  properties:
  - type: OpenAPI
    url: openapi/loopme-advertiser-reporting-api-openapi.yml
  - type: Overlay
    url: overlays/loopme-advertiser-reporting-api-overlay.yaml
  - type: Documentation
    url: https://wiki.loopme.cool/publishers/reporting-api
- aid: loopme:loopme-publisher-reporting-api
  name: LoopMe Publisher Reporting API
  description: The Publisher Reporting API from LoopMe — 1 operation(s) for publisher reporting.
  humanURL: https://wiki.loopme.cool/publishers/reporting-api
  baseURL: https://reports.loopme.com/api/v1
  tags:
  - Publisher Reporting
  properties:
  - type: OpenAPI
    url: openapi/loopme-publisher-reporting-api-openapi.yml
  - type: Overlay
    url: overlays/loopme-publisher-reporting-api-overlay.yaml
  - type: AgentSkill
    url: skills/loopme-pull-reporting.md
  - type: Documentation
    url: https://wiki.loopme.cool/publishers/reporting-api
common:
- type: Website
  url: https://loopme.cool
- type: AgenticAccess
  url: agentic-access/loopme-agentic-access.yml
- type: DeveloperPortal
  url: https://wiki.loopme.cool/
- type: Documentation
  url: https://wiki.loopme.cool/
- type: APIReference
  url: https://wiki.loopme.cool/publishers/reporting-api
- type: Blog
  url: https://loopme.ai/news-blog/
- type: Support
  url: https://www.loopme.io/support/
- type: GitHubOrganization
  url: https://github.com/loopme
- type: PrivacyPolicy
  url: https://legal.loopme.com/privacy-center
- type: TermsOfService
  url: https://legal.loopme.com/legal-centre/terms-of-use
- type: SDKs
  url: packages/loopme-packages.yml
- type: Packages
  url: packages/loopme-packages.yml
- type: Authentication
  url: authentication/loopme-authentication.yml
- type: ErrorCatalog
  url: errors/loopme-error-codes.yml
- type: Conventions
  url: conventions/loopme-conventions.yml
- type: Lifecycle
  url: lifecycle/loopme-lifecycle.yml
- type: X-MCPServerCandidate
  url: mcp/loopme-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: DomainSecurity
  url: security/loopme-domain-security.yml
- type: DataModel
  url: data-model/loopme-data-model.yml
- type: ChangeLog
  url: changelog/loopme-changelog.yml
- type: LLMsTxt
  url: llms/loopme-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: AgentSkill
  url: skills/loopme-request-ad-s2s.md
- type: Plans
  url: plans/loopme-plans-pricing.yml
- type: RateLimits
  url: rate-limits/loopme-rate-limits.yml
- type: Sandbox
  url: sandbox/loopme-sandbox.yml
- type: Conformance
  url: conformance/loopme-conformance.yml
- type: Compliance
  url: https://legal.loopme.com/privacy-center
- type: TrustCenter
  url: security/loopme-trust-center.yml
- type: Components
  url: components/loopme-components.yml
- type: Login
  url: https://loopme.ai/product-logins/
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 12
  pass: local-v1
x-lifecycle:
  state: shuttered
  reason: domain-does-not-resolve
  observed: '2026-09-27'
  detail: The company's own domain returned no A or AAAA record when probed. This is an observation about the domain, not
    a request from the company.
  indexed: false

LoopMe API — frequently asked questions

Does LoopMe have an API?

Yes. APIs.io lists 3 APIs from LoopMe, including LoopMe S2S Ad Serving API, LoopMe Advertiser Reporting API and LoopMe Publisher Reporting API.

Is there an OpenAPI specification for the LoopMe API?

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

How do I authenticate with the LoopMe API?

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

Is the LoopMe API ready for AI agents?

LoopMe has a Kin Score of 39.9 out of 100 (developing) and an Agent Readiness score of 34.0 (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/loopme"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/loopme/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.