What your model can and can’t do
Your model operates inside the allowance, and the limits are enforced on-chain. We cannot break your rules, and neither can your model — only you can change them.
- It can call the waypoints you granted, spend within the cap, and receive only the tokens you allowed.
- It can’t move funds to another wallet, exceed the budget, touch tokens you haven’t approved, or grant itself new permissions. The approval that sets its allowance can only be signed by you.
- It can ask. A model that wants more budget or a new capability files a request. The request shows up in your dashboard; nothing changes unless you approve and sign it. Your model can propose; only you can permit.
When an attempt to execute is blocked, the refusal is typed and specific, so the model knows exactly what happened and what would fix it:
{
"code": "EXCEEDS_ALLOWANCE",
"error": "this call would spend $50.00 but only $8.00 of the budget remains",
"remedy": "reduce the amount, or ask the owner to raise the cap with waypoint_request_budget"
}Refusals your model might see
| Code | What happened | What fixes it |
|---|---|---|
UNAUTHORIZED | The credential is missing, wrong, or was rotated | Paste the current credential |
NO_DELEGATION | The session has no allowance for this waypoint | Grant one in the dashboard |
EXCEEDS_ALLOWANCE | The call would spend past the remaining budget | Smaller call, or approve a raise |
TOKEN_NOT_ALLOWED | The output token isn’t in the granted set | Add the token to the allowance |
SESSION_MISMATCH | The call names an allowance owned by another session | Use the session’s own grants |
PAUSED | The owner (or Waypoint) engaged the kill switch | Wait; nothing executes while paused |
A refused call never charges a fee and never reaches the chain. Every quote and balance check is free, for you and for it — reading never costs anything.