How Aident Loadout Credits, BYOK, and Action Pricing Work

Aident Loadout has four separate cost decisions: how your account is funded, what one Action is priced to cost, whether that price crosses your approval threshold, and whether Aident or your own provider account funds the external call.

The practical rule is simple: check the current plan catalog, inspect the exact Action, preflight the exact input, and approve only the quote you understand. A user-owned credential can reduce the Aident credit deduction to zero for a supported Action, but the provider may still bill your account. BYOK changes who pays the provider. It does not make external work free.

This guide explains those boundaries without assuming that every Action has the same price or that today's plan allowance will never change.

The Short Answer

Start with the installed public aident CLI:

aident account auth status
aident vault vault --action status
aident billing billing --action plans --surface loadout

Then discover and inspect the Action for the job:

aident capabilities search \
  --query "search current public sources for a market brief" \
  --targetEnv staging

aident capabilities get \
  --name "<exact-canonical-action-name>"

Preflight the exact input before execution:

aident capabilities preflight \
  --name "<exact-canonical-action-name>" \
  --input '<exact-input-json-from-the-current-schema>'

The preflight should tell you whether the input is valid and whether the estimate is exact, a range, or unavailable. If the estimate meets your configured threshold, it also returns a one-time approval path. Do not execute an expensive or unbounded Action merely because discovery succeeded.

The Four Cost Layers

Confusion starts when several different balances and bills are described as one price. Keep these layers separate.

These layers interact, but they are not substitutes for one another. A paid plan does not make every Action free. A free Action does not require a paid quote. A personal credential may avoid an Aident credit deduction while still consuming your provider quota. An approval setting controls spending authorization, not authentication or Action risk.

Layer 1: Plan Funding and Credit Boosts

The plan catalog is the source of truth for current recurring plans, included monthly credits, and any one-time credit boosts. Ask the CLI instead of copying a price from an old screenshot:

aident billing billing --action plans --surface loadout

The response identifies the current plan entries, monthly credit allowances, supported credit boosts, display prices, and checkout inputs. In the August 12, 2026 verification run, the catalog returned a free entry, a recurring paid entry, and three one-time boost sizes. Those names, amounts, and allowances can change, so this article does not turn that snapshot into a permanent promise.

Plan funding answers how the wallet receives credits. It does not answer the price of the next Action. That price belongs to the active Action definition and, for dynamic work, the normalized input.

Use a recurring plan when your workload is predictable enough that a monthly allowance is useful. Use a one-time boost for a temporary burst after you understand the Actions involved. Start free when the selected Actions are free, personally funded, or you are still validating the workflow.

Layer 2: The Exact Action Price

Loadout prices integration operations, not vague integration names. One provider can expose administrative reads, searches, media generation, and long-running research with very different costs.

An Action can use one of several pricing shapes:

• Free: the operation has an explicit zero-credit rule.

• Flat rate: one successful call has a known price.

• Dynamic: the input determines the quote, such as video duration, resolution, search mode, or provider usage units.

• Runtime range: hosted command execution can settle from actual compute, memory, and network use.

• Unavailable preflight estimate: the runtime cannot safely calculate an upper bound before dispatch.

That is why the exact canonical Action name matters. A root integration label is not a price contract, and a search-result summary is not enough to authorize execution.

Inspect the current schema first:

aident capabilities get \
  --name "<exact-canonical-action-name>"

Check the required fields, operation type, risk level, required integration, and pricing summary. Then preflight the same input you intend to execute. Changing a price-relevant field after preflight means you are looking at the wrong quote.

Layer 3: Preflight and Credit Approval

Preflight validates and prices without dispatching the provider operation. It does not reserve wallet credits, create usage, or prove that the external provider will succeed.

A useful preflight result answers three things:

1. Is the input valid against the current Action schema?

2. Is the estimate exact, bounded by a range, or unavailable?

3. Does the quote require approval under this account's settings?

For an exact or bounded estimate below your threshold, you can decide whether the result is worth the cost. When the estimate meets the threshold, Loadout can return a quote-bound approval token for the identical Action and input. That token is for credit approval only.

Risk acknowledgement is a separate control. A write Action may require acknowledgement because it changes external state even when its credit price is zero. Conversely, a read-only research Action can be expensive without having a high external-write risk. Do not use a credit approval token as evidence that a consequential write is safe.

If a dynamic estimator reports that the price is unavailable or unbounded, stop unless the user explicitly approves that uncertainty. In this research cycle, an Ahrefs keyword input was valid, but the dynamic resolver could not produce a bounded estimate before execution. The run stopped at the configured 100-credit approval boundary instead of bypassing Loadout or calling the provider directly.

Layer 4: Aident-Managed Access Versus BYOK

Some Actions can run with Aident-managed provider access. Others require or permit a credential that you own and store through Aident Vault.

The funding paths differ:

Do not infer BYOK support from the integration name. Check Vault readiness and the exact Action contract:

aident vault vault --action status
aident capabilities get --name "<exact-canonical-action-name>"

Keep provider secrets in Vault. Do not paste an API key, OAuth code, cookie, or access token into a prompt, shell history, article draft, or repository. Give AI Agents API Access Without Exposing Keys explains the credential boundary in detail.

BYOK is often useful when your organization already has provider credits, negotiated rates, data residency requirements, or a required account configuration. Aident-managed access is useful when you want a reviewed integration path without maintaining that provider credential yourself. Compare the complete route, not just one visible number.

A Worked Decision Sequence

Suppose an agent needs current web research for a ten-result brief.

First, confirm the account and available connections:

aident account auth status
aident vault vault --action status

Second, search by job and inspect the returned exact Action:

aident capabilities search \
  --query "search the current web and return ten source links" \
  --targetEnv staging

aident capabilities get \
  --name "composio:exa_tools:exa_search"

Third, preflight the final query, result count, search mode, and content options. In the August 12 research run, one current web search input returned an exact quote of 0.7 Aident credits. The provider was not dispatched during preflight.

Fourth, compare that quote with the value of the output and your approval settings. If the Action uses a personal credential, verify whether the final Aident deduction is expected to be zero and review the provider's own billing. If the input changes from a fast search to a deep research job, preflight again.

Finally, execute only after the cost and consequence are understood:

aident capabilities execute \
  --name "composio:exa_tools:exa_search" \
  --input '{"query":"AI agent pricing","type":"fast","numResults":10,"userLocation":"US"}'

Afterward, use Loadout Audit to confirm what ran and what was charged. Do not treat a reserved estimate as the final receipt for a metered runtime.

Common Pricing Mistakes

Treating a plan price as unlimited usage

A recurring plan funds a credit allowance. Each paid Action still has its own rule, and a dynamic Action can consume more than a simple read.

Assuming BYOK means free

BYOK can make the Aident Action deduction zero. The provider can still charge your account or consume contracted quota.

Approving an integration instead of an input

Dynamic prices can depend on duration, resolution, result count, mode, or other normalized fields. Approve the exact input, not a general intention to use the provider.

Mixing credit approval with risk approval

Credit approval controls spend. Risk acknowledgement controls permission for consequential behavior. A zero-credit external write can still require careful review.

Copying a stale price into automation

Plans and Action definitions can change. Query the plan catalog and preflight immediately before a material run. Store the final Audit receipt, not an old blog screenshot, as execution evidence.

Bypassing the integration layer when pricing is uncertain

An unavailable estimate is a reason to stop or request explicit approval. It is not permission to call a provider SDK directly and lose the same contract, Vault, approval, and Audit boundaries you were trying to evaluate.

Which Funding Route Should You Choose?

Use this decision order:

1. Define the finished job and the maximum acceptable cost.

2. Discover the current exact Action and inspect its schema.

3. Check whether the operation is free, flat-rate, dynamic, or runtime-metered.

4. Check whether Aident-managed access or a personal Vault credential is available.

5. Preflight the exact input.

6. Choose recurring funding or a one-time boost only after you understand likely usage.

7. Execute with the required credit approval and separate risk acknowledgement.

8. Verify the final charge in Audit.

For a broader budget policy, read How to Set AI Agent Cost Guardrails and Stop Runaway API Bills. To run a complete first workflow, continue with How to Use Aident Loadout: Your First Task Done in 10 Minutes.

Review Pricing Before Your First Paid Action

Start with the current plan catalog, then preflight one useful Action with the exact input you intend to run. You should be able to explain which account funds the provider, what Aident can deduct, what requires approval, and where the final receipt will appear before execution begins.

Review current Loadout pricing and start setup.

Sources

• Aident Loadout pricing

• Aident Loadout setup for agents

• Aident Loadout overview

• Aident Loadout setup guide

• AI Agent Cost Guardrails

• MCP API Keys vs OAuth

Review this article when plan entries, credit boosts, Action pricing shapes, preflight approval behavior, Vault funding routes, or Audit receipts change.