DNAbyD3Docs

Rules and pricing

Let agents in, stop them, ask for human verification by DNA, or charge a price you set.

A rule says what happens to a visit on some of your pages. Write rules under Rules in the dashboard; what priced pages earn is under Earnings.

You want to…Asks forCosts the visitor
Keep some agents off a pageBlockn/a
Make an exception to a broader ruleLet inNothing
Know a person stands behind every agentRequire a humanNothing
Get paid when agents take a pageChargeThe price
Charge agents, and let verified people in freeCharge or require a humanThe price, or nothing once verified

Each site's rules apply top to bottom, and the first rule that matches a visit decides it. A visit no rule matches is let in.

Add a rule

  1. Open Rules and click New rule.

  2. Fill in the steps:

    StepValue
    1. What it coversPage, API or MCP server. See Pages, APIs and MCP servers.
    2. What happensSee What a rule asks for.
    3. To whomSee Who it applies to.
    4. WhereSite (only sites DNA has seen traffic for), and Paths such as /premium, each with a Match.
    5. Only whenOptional. See Only when.
    6. PriceIn dollars per request, such as 0.001. Only when the rule charges.
    How to startDry run or Turn on now. See Dry runs.

    Beside the form, If this rule had been on for the last 7 days counts the requests on those paths the rule would have stopped, asked, or let in, split by Verified, Name only, Impersonator, No name and people. Narrow the rule until the figure looks right.

  3. Click Start dry run or Turn on now. The rule goes to the bottom of the site's list.

  4. Use the arrows beside a rule to move it up or down.

A saved change usually reaches your site straight away. If it doesn't, the dashboard says so, and it lands within 15 minutes.

Pages, APIs and MCP servers

CoversUse it forAn unpaid request gets
PagePages people and agents readWhatever the rule asks for, below
APIAn endpoint only software callsA 402 in JSON listing every way to pay. Never a redirect, a page or a browser check
MCP serverTool calls to an MCP serverA tool result asking for payment. Connecting and listing tools stay free

An API or MCP rule can Let in, Block or Charge, and applies to every caller: narrow it under Only when, by agent, identity or anything the request carries. On an MCP server, the MCP tool condition narrows a rule to one tool. A person who opens an API path in a browser sees JSON, so mark a path as an API only if no one reads it in a browser. Agents paying for MCP calls follow Pay for MCP tool calls.

What a rule asks for

Asks forWhat a matching visit getsCharged
Let inThe page. No rule below it is checked.No
BlockA 403. Your site never sees it.No
Require a humanThe page once DNA confirms a person is behind it; DNA's verification otherwise. No price, no wallet.No
ChargeThe page if it pays; a payment request otherwise.The price
Charge or require a humanThe page if it pays, or free once DNA confirms a person is behind it.The price, unless verified

Human verification is not an account on your site, and your site gets no personal details: the visitor, or the person an agent works for, confirms with their DNA account. A person's browser is sent back without a click once confirmed. An agent's request still waits for the person to approve it on DNA, where the page is marked free. A verification approved for a free page never pays for a priced one: that page asks again.

Dry runs

A new rule starts as a Dry run. It changes nothing for visitors: the Rules list shows what it would have done, such as Would have blocked 120 or Would have asked 40. Click Turn on beside the rule when the figure looks right, or edit it and set Status to On; setting it back to Dry run stops it at any time.

A dry run counts only the visits it would have decided: those no rule above it matches, whether that rule is on or a dry run. Order a dry run the way you would order it switched on.

Who it applies to

ChoiceApplies to
AI agents (default)Every agent DNA can identify. People browsing are left out.
Everyone, including peopleEvery visit. Use it as a paywall, or human verification for everyone.

Under AI agents, Leave out agents built for search indexing is ticked for a new rule that doesn't let agents in, so Googlebot, Bingbot and other search crawlers keep reading the page. It leaves out only Verified ones: a search crawler that is Name only or an Impersonator still meets the rule. Untick it to cover search crawlers too.

To switch on a rule that stops everyone, tick Stop people too: nothing about a visit tells a person from an agent DNA can't name.

Only when

Only when narrows a rule to visits that meet its conditions: the agent, its identity (Verified, Name only, Impersonator, No name), what it's built for, the country, the IP address, a query string parameter, a header, or a cookie. Every condition in a set must hold, and any one set is enough. A negative condition such as is not also matches a visit that sends no value at all.

Header and cookie conditions need the Cloudflare adapter 0.10.0 or the Vercel middleware 0.9.0 or later. A set doesn't match when it reads a header or cookie your site keeps back from DNA, and the rule can still apply through another set. A value over 2,048 characters counts as sent but unread: it never gets a visitor past a Block or a charge, and a Let in set doesn't match on it.

Write a cookie or query string value the way your site sets it, not the way it travels: a rule for premium plus matches a cookie sent as premium%20plus. A header value is matched exactly as sent, and a + in a cookie is matched as a plus, not a space.

Anyone can set a query string, a header or a cookie, or send from an IP address, so a Let in rule that rests only on one asks you to tick Let in anyone who sends this before it switches on.

Every request a rule decided, or would have, is in Requests: click a rule's matched count, or read the Rule column.

How you get paid

PaidWhere the money goes
By cardD3 charges the payer and pays you your share once the month closes
In cryptoThe full price lands in your organization's wallet as each payment settles
  • Earnings shows what was paid, Available to withdraw (crypto) and your monthly card statements.
  • Only owners withdraw. A transfer can't be undone, so the dashboard reads the amount, network, and address back before Send.
  • DNA creates a wallet with your organization. If yours is missing, the checklist on Rules creates it. Charging needs a wallet; human verification doesn't.

Path matching

MatchCovers
This path only/premium, and nothing else
This path and everything under it/premium and /premium/report. Whole segments only, so never /premiumfoo.
Matches a patternPaths the pattern matches end to end: ^/archive/\d{4}$ covers /archive/2024, not /archive/2024/june

A rule can list several paths; any one of them is enough. The query string is ignored by the path: /report?page=2 is priced as /report. To narrow by it, add a query string condition under Only when.

The preview beside the form leaves out pattern paths and IP address and query string conditions, and says so. The dry run applies everything.

What counts as a request

  • Each request that reaches DNA is charged. A page a browser serves from its own cache is free, so your Cache-Control decides how often that happens.
  • Rules apply in order. A Block rule above a price wins, and nobody pays past it.
  • A page is served to a paying request only once the payment settles.

Roles

RoleCan
OwnerAdd, edit, move, and switch on rules; withdraw
AdminAdd, edit, move, and switch on rules
MemberSee rules and what they did

Charge column

Requests shows one value per request on a page with a price.

Normal values

ValueMeaning
would have chargedA dry run. Nothing taken; the request reached your site.
asked to payThe caller was asked to pay and hasn't come back yet.
paidThe payment cleared and the request reached your site.
refusedA payment was presented and refused. Nothing was served.
already spentThat payment had been used before. Nothing was served.

Values that need action

Nothing is charged on any of these.

ValueMeaningReached your site?
no currency setThe rule charges but has no currency to accept payment in, or asks for human verification while DNA pay is off.Yes, free
path unclearDNA couldn't tell which path was requested.No, if the rule that applies was on
provider downDNA couldn't reach the payments provider.No
couldn't checkDNA couldn't check the payment for reuse, so didn't settle it.No
not set upPayments aren't set up on DNA's side.No
prices unreadDNA couldn't read the rules for this site.Yes, free
error on our sideA DNA failure before the charge was decided.No for paying requests, yes for the rest

Limits

LimitValue
Rules per organization50

Building the agent side? See Pay with DNA and Pay with x402.

On this page