Pricing

See what Artax charges, what stays free, and what to expect before you turn on paid usage.

Billing Model

What Artax bills.

This page explains what is billed, what stays included, what becomes prepaid on mainnet-beta, and the exact amounts current actions consume.

Not billedIncluded sandboxPrepaid mainnet-betaVisible in dashboard

Billing follows what you actually do.

Artax meters usage by route, action, project, API key, and cluster. This page turns that into a clear customer view so you can tell what is free, what is prepaid, and what does not count against your balance.

Never billed

Public status routes, admin routes, and quote-only or non-executed outcomes do not consume customer balance.

Included in the sandbox

Current non-mainnet usage stays included instead of burning prepaid balance, but allowance and abuse limits still apply.

Prepaid on mainnet-beta

Paid mainnet-beta advisory review reduces prepaid USDC balance and shows up in the dashboard. Most account and dashboard actions remain included.

Execution requests stay separate

Execution request routes are not priced like simple advisory review. They follow their own approval and sponsorship flow.

Open usage Open pricing Open quickstart

Billing boundaries

Things the billing model will not do

Unused prepaid balance does not expire solely due to time passage.
Billing mode is visible in the usage dashboard by billing mode, route family, usage unit, project, API key, and cluster.
Devnet and other non-mainnet environments do not silently fall through to prepaid continuation when the current policy says to wait.
Shared commercial balance and cluster-attributed usage records remain separate concepts.

What this page is not

This page explains current billing behavior. It is here to make charges predictable, not to bury you in accounting language.

No charge

Not billed

Public status and discovery routes

Public health, public config, and public trust reads do not consume customer balance or included allowance.

Operator-only control routes

Operator-only routes are operational tooling and must never bill a customer balance.

Non-executed or denied outcomes

Quote-only calls, preflight denials, unsupported requests, and non-executed intents are not billed to customers.

Included

Current non-mainnet customer usage

Current non-mainnet usage stays included instead of reducing prepaid balance. Free-tier and anti-abuse limits still apply, and exhaustion becomes a wait-state where the current policy requires it.

Prepaid

Current paid mainnet-beta usage

Current paid mainnet-beta advisory review is recorded as prepaid usage and reduces the shared prepaid USDC balance, while most account and dashboard actions remain included today.

Separate flow

Execution requests

Execution-capable submit routes

Execution-capable submit routes are not marketed as simple advisory prepaid billing. They remain governed by sponsorship eligibility, reviewed intent, and execution economics.

Route classes

Route families and how they behave

Public status and discovery routes

public_unmetered

Public health or static-discovery route that should not consume prepaid balance.

not billed

Example routes

route.api.healthroute.api.config_publicroute.api.trust_metrics

Builder review routes

builder_review_metered

Builder-facing review route intended for account-scoped sandbox/free-tier or prepaid advisory balance accounting.

not billedincludedprepaid

Example routes

route.api.analyze_transferroute.api.analyze_swap

Account and dashboard routes

account_commercial_metered

Initial local-first account, project, API-key, funding, and usage routes that meter against the prepaid account ledger model where appropriate.

includedprepaid

Example routes

route.api.account.get_onboarding_stateroute.api.account.get_overviewroute.api.account.get_funding_statusroute.api.account.get_balance+19 more

Execution request routes

execution_request_not_advisory_billed

Execution-capable route where sponsored execution remains the primary revenue engine rather than simple advisory billing.

not billedseparate execution flow

Example routes

route.api.submit_transferroute.api.submit_transaction

Admin routes

operator_internal_not_customer_billed

Operator-only routes that should never bill a customer balance.

not billed

Example routes

route.api.system_metricsroute.api.system_rpc_healthroute.api.apps_listroute.api.account.record_funding_event+4 more

Free-tier behavior

Current advisory allowance policy

Free-tier access is available immediately after account creation, but it is sandbox-oriented, authority-limited, account/project/API-key windowed, and subject to anti-farming controls with prepaid fallback where configured.

advisory_review_request

24-hour window with 250 account, 100 project, and 50 API-key units.

Exhaustion behavior

What happens when the advisory allowance runs out

devnetwait state

On devnet, allowance exhaustion becomes a wait-state until the current window resets rather than silently continuing as prepaid usage.

testnetwait state

On testnet, allowance exhaustion becomes a wait-state until the current window resets rather than silently continuing as prepaid usage.

mainnet-betaprepaid continuation

On mainnet-beta, advisory free-tier exhaustion may continue as prepaid usage when the current policy allows it and prepaid balance is available.

Unit pricing and reporting labels

What each current action costs when prepaid billing applies

Each current action below consumes the listed usage units when it is metered. Non-mainnet still stays included by policy, but mainnet-beta prepaid deduction uses the exact amounts shown here.

Advisory review carries a small prepaid charge, execution requests stay on a separate approval path, and most account and dashboard actions still remain included in the current product.

Review and execution-prep requests

These are the request units most closely tied to live review traffic. Advisory review is prepaid, while execution requests follow their own approval path.

advisory_review_request

1 unit

One advisory analyze request against a supported route family.

Units consumed

Mainnet-beta prepaid amount

0.00075 USDC

sponsored_execution_request

1 unit

One sponsored execution request evaluated under bounded sponsorship policy.

Units consumed

Mainnet-beta prepaid amount

0 USDC

Account and funding reads

These units cover account posture, balance state, funding status, and current balance-ledger reads.

account_onboarding_state_read

1 unit

One canonical account onboarding-state read including verification status, default project, sandbox-key summary, trust tier, and authority posture.

Units consumed

Mainnet-beta prepaid amount

0 USDC

account_overview_read

1 unit

One canonical account-overview retrieval event including trust, authority, route-limit, and restriction posture.

Units consumed

Mainnet-beta prepaid amount

0 USDC

account_funding_status_read

1 unit

One canonical account funding-status retrieval event including balance state, funding state, and funded-upgrade posture.

Units consumed

Mainnet-beta prepaid amount

0 USDC

account_balance_read

1 unit

One machine-readable account-balance read against the prepaid balance surface.

Units consumed

Mainnet-beta prepaid amount

0 USDC

account_balance_adjustment_read

1 unit

One recent account balance-adjustment ledger read showing funding credits, pending releases, and usage-linked prepaid deductions.

Units consumed

Mainnet-beta prepaid amount

0 USDC

account_balance_ledger_read

1 unit

One time-range-aware account balance-ledger read, including funding credits, pending releases, usage debits, and daily movement buckets.

Units consumed

Mainnet-beta prepaid amount

0 USDC

funding_instruction_issue

1 unit

One funding-instruction retrieval event for a funded account flow.

Units consumed

Mainnet-beta prepaid amount

0 USDC

funding_event_query

1 unit

One recent account funding-event history query.

Units consumed

Mainnet-beta prepaid amount

0 USDC

Projects and API keys

These units cover listing, creating, updating, issuing, and revoking projects or API keys.

project_listing_operation

1 unit

One project-list retrieval event scoped to an Artax account.

Units consumed

Mainnet-beta prepaid amount

0 USDC

project_creation_operation

1 unit

One new project creation event scoped to an Artax account.

Units consumed

Mainnet-beta prepaid amount

0 USDC

project_metadata_update_operation

1 unit

One governed project metadata mutation for a supported display-name update.

Units consumed

Mainnet-beta prepaid amount

0 USDC

api_key_listing_operation

1 unit

One API-key inventory retrieval event scoped to an Artax account.

Units consumed

Mainnet-beta prepaid amount

0 USDC

api_key_creation_operation

1 unit

One account API-key creation event bounded by current caller scopes and authority.

Units consumed

Mainnet-beta prepaid amount

0 USDC

funded_advisory_key_issue_operation

1 unit

One explicit funded-advisory API-key issuance event once credited prepaid balance is available.

Units consumed

Mainnet-beta prepaid amount

0 USDC

api_key_revocation_operation

1 unit

One account API-key revocation event.

Units consumed

Mainnet-beta prepaid amount

0 USDC

Reporting and history

These units already show up in the usage and activity sections of the dashboard.

account_activity_ledger_query

1 unit

One recent unified account activity-ledger query, including category counts plus governed funding, restriction, lifecycle, authority, request-error, and audit summaries.

Units consumed

Mainnet-beta prepaid amount

0 USDC

account_audit_event_query

1 unit

One recent user-safe account audit-event history query, including safe event-type counts and account change summaries.

Units consumed

Mainnet-beta prepaid amount

0 USDC

request_error_event_query

1 unit

One recent user-safe account request-error history query, including top-level category counts and denial-relevant guidance fields.

Units consumed

Mainnet-beta prepaid amount

0 USDC

project_metadata_event_query

1 unit

One recent project metadata-event history query.

Units consumed

Mainnet-beta prepaid amount

0 USDC

restriction_event_query

1 unit

One recent account restriction-event history query.

Units consumed

Mainnet-beta prepaid amount

0 USDC

api_key_restriction_event_query

1 unit

One recent API-key restriction-event history query.

Units consumed

Mainnet-beta prepaid amount

0 USDC

project_restriction_event_query

1 unit

One recent project restriction-event history query.

Units consumed

Mainnet-beta prepaid amount

0 USDC

usage_reporting_window

1 unit

One usage-summary reporting window returned to a caller.

Units consumed

Mainnet-beta prepaid amount

0 USDC

usage_breakdown_read

1 unit

One project-aware and time-range-aware usage-breakdown read, including paid-balance consumption buckets.

Units consumed

Mainnet-beta prepaid amount

0 USDC