|

Measurement partners

Affiliate networks, dashboard tools, and analytics platforms can read OA telemetry data on behalf of content owners who grant them access. No proprietary integration - you query the same API content owners use.

If you also need to write events on behalf of content owners (for example, reporting retrievals from a content marketplace, or reporting link_click engagements from a landing page), see the marketplaces and networks guide.

Building a dashboard with AI?

Drop this URL into Claude, ChatGPT, Cursor, or any other LLM:

https://openattribution.org/docs/api.md

That is the full API reference as a single self-contained Markdown file - everything the model needs to scaffold a starter dashboard against your delegated telemetry. Or jump straight in:


How it works

text
Content owner                    Measurement partner
     |                                  |
     |  1. Grants delegation            |
     |  (dashboard or API)              |
     |                                  |
     |                                  |  2. Queries content-owner endpoints
     |                                  |     ?delegated_from={owner_org_id}
     |                                  |
     |           OA gateway             |
     |      checks delegation table     |
     |      returns owner's data        |
     |                                  |

The content owner grants you telemetry:read access via the OA dashboard or API. You authenticate with your own API key and pass delegated_from on content-owner endpoints to access their data.


Getting started

First, set up your platform org
Measurement partners register as platforms - that's the role that holds delegated read access. The platform setup guide covers sign-up, approval, finding your organisation ID, and minting an API key (scope it to telemetry:read here). Then come back for the delegation flow below.

1. A content owner grants you access

The content owner goes to Measurement partners in their OA dashboard and enters your organisation ID (the one from /partners). This creates a delegation - immediately active, revocable at any time.

Alternatively, they can use the API:

json
POST /api/v1/identity/delegations
{
  "grantee_org_id": "your-org-id",
  "scopes": ["telemetry:read"]
}

2. Query their telemetry

Use the same content-owner endpoints, adding your authentication and the delegated_from parameter:

text
GET https://api.openattribution.org/content-owners/summary?delegated_from={grantor_org_id}&since=2026-03-01
X-API-Key: oat_pk_yourkey...

You get the same response a content owner would see - total events, agent breakdown, top URLs. All three content-owner endpoints support delegation: /content-owners/summary, /content-owners/events, and /content-owners/urls. Full request/response shapes are in the API reference.


What you can build

AI traffic dashboards

Show content owners which AI agents are fetching their content, how often, and which URLs. Net-new data that doesn't exist in any affiliate dashboard today.

Attribution models

When citation and outcome data flows, build multi-touch attribution across the content influence chain. Which content was retrieved, cited, and led to a purchase.

Aggregated reporting

Query across all content owners who have granted you access. Build network-wide views of AI agent activity.

Data isolation
Each delegation is a separate grant. You can only access data for content owners who have explicitly granted you access. No cross-content-owner aggregation happens on the OA side - you aggregate across your own delegations.

Managing delegations

List your delegations

text
GET /api/v1/identity/delegations?role=grantee
X-API-Key: oat_pk_yourkey...
json
[
  {
    "id": "...",
    "grantor_org_id": "...",
    "grantee_org_id": "your-org-id",
    "grantor_name": "Wirecutter",
    "grantee_name": "Your Network",
    "scopes": ["telemetry:read"],
    "created_at": "2026-03-24T...",
    "revoked_at": null
  }
]

Use the grantor_org_id from each delegation as the delegated_from parameter when querying content-owner endpoints.

On the roadmap
Webhook delivery (OA pushes events as they arrive) and bulk delegation APIs for onboarding large content-owner bases are next on the roadmap.