Skip to main content
POST
Declare a wallet you hold outside Dakota

Authorizations

x-api-key
string
header
required

Headers

x-idempotency-key
string<uuid>
required

Unique key to ensure request idempotency. If the same key is used within a certain time window, the original response will be returned instead of executing the request again.

Body

application/json

A wallet held outside Dakota, to count toward this client's fee.

address
string
required

An EVM address on Base.

Example:

"0x1234567890123456789012345678901234567890"

Response

The wallet now counts.

A wallet held outside Dakota that counts toward this client's fee.

chain
string
required

CAIP-2 chain id. Always Base, because RD exists only there.

Example:

"eip155:8453"

address
string
required

Lowercase. EVM addresses are case-insensitive.

counting_from
string<date-time>
required

The instant this wallet started counting. Normally the first instant of the UTC month it was added in — a wallet added on 20 September earns for all of September.

It is later than that when the address was already counting for somebody earlier in the same month, either because another client had declared it or because Dakota held it in custody; it then resumes at the instant that ended. Never an earlier month, so a priced month is unaffected.

Parse this as an instant, not as a date. It is RFC 3339 and may carry a non-UTC offset, so reading the date part directly can give the previous day — and, for a month boundary, the previous month. Convert to UTC before comparing it to a month.