Rules and pricing

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.

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:

   Step	Value
   1. What happens	See What a rule asks for.
   2. To whom	See Who it applies to.
   3. Where	Site (only sites DNA has seen traffic for), Path such as /premium, and Match.
   4. Price	In dollars per request, such as 0.001. Only when the rule charges.
   How to start	Dry 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 that path 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.

What a rule asks for

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 stopped 120 or what a price would have earned. 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

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.

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

• 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

The query string is ignored: /report?page=2 is priced as /report.

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

Charge column

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

Normal values

Values that need action

Nothing is charged on any of these.

Limits

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