# Explore paid access for agents using your data.

Agents already read your most valuable material for free. If a known partner would pay for it, identity evidence, access rules and a usage record could turn some of that traffic into revenue.

For data providers and publishers with material agents would pay for.

Status: Exploring

## Agent traffic is a cost today. Some of it could be a customer.

Serving agents costs bandwidth and compute, and the value of your data leaves with them. A specific dataset with an identifiable buyer is where paid access could start.

A directory entry or a user-agent name is not payment authority. Who is asking, what they may use, and how it is billed all have to line up, and the billing stays in your own system.

## Where 500,000 agent requests could lead

- Agent requests a month: 500,000
- From identifiable agents: 300,000
- From a known partner: 30,000
- Revenue potential a month: $300

Illustrative example. 60% from identifiable agents; 10% of those from a known partner; $0.01 per request. Demand unproven. Hypothetical.

## The same requests, priced.

| | Reported | With evidence |
|---|---|---|
| Requests served free | 500,000 | 470,000 |
| Priced requests | 0 | 30,000 |
| Monthly revenue | $0 | $300 |

Illustrative example.

## Your numbers

Revenue potential = requests × share identifiable × share from a willing partner × price.

## One request, from identity to invoice.

- Caller: research-agent.partner.example
- Identity: Signature verified
- Entitlement: Licensed: pricing dataset
- Usage record: 1 request, $0.01, to your billing

Double Agent could supply the identity evidence and the usage record. Authorization and payment stay with you.

## How it fits

1. **Pick the resource.** One dataset or service with a plausible buyer and permitted use.
2. **Identify the caller.** Use supported identity evidence alongside account authorization.
3. **Record usage.** Count what each authorized agent used.
4. **Bill in your system.** Reconcile usage with your own billing and payments.

## What your team can do

- **Find the payer.** Talk to one known partner about a paid unit.
- **Set access rules.** Decide what is free, priced or refused.
- **Run a narrow pilot.** One resource, one partner, before any broad claims.

## Before you start

### Is there a Double Agent payment rail?

No. This is an exploration. Payments and licensing stay in your own systems.

### Can I charge every crawler that visits?

No. Crawler traffic is not evidence that anyone will pay, and fees are not collectible from arbitrary crawlers.

### Does a registry listing prove who an agent is?

No. A listing or user-agent name is not payment authority; use verified identity and your own authorization.

### What would prove demand?

A real prospective payer, a priced unit, access rules and a way to reconcile usage.

[Discuss paid agent access](mailto:support@doubleagent.so?subject=Use%20case%3A%20Paid%20access%20for%20agents)

- [Double Agent Identity](https://doubleagent.so/identity/)
- [Double Agent Registry](https://doubleagent.so/registry/)
- [All use cases](https://doubleagent.so/use-cases/)