Which tool answers: mechanics questions
Deciding with the data maps five financial decisions (exit, branch cost, policy, backing, participants) to routes and tools. This page is the companion for mechanics questions, "how does X work" rather than "what should I do." It points each one at the page that explains it and the route or tool that reports its current state.
| Question | Explained in | Live state from |
|---|---|---|
| How do charter withdrawals (exits) work? | Exits and the resolution fee curve | GET /v1/charters/{id}/exit-quote, 1s_std_exit_quote |
| What is the multiplier epoch policy? | Protocol overview and issuance | GET /v1/policy/current, 1s_std_policy_current |
| How does a branch actually earn STANDARD? | Protocol overview and issuance | GET /v1/branches/summary, 1s_std_branches_summary |
| How does the license auction price work day to day? | Charters, branches, and licenses | GET /v1/auctions/current, 1s_std_auctions_current |
| What's the difference between buying a license and buying a charter? | Charters, branches, and licenses | GET /v1/branches/license-cost, 1s_std_license_cost |
| How is the resolution fee calculated? | Exits and the resolution fee curve | GET /v1/exit-pressure/current, 1s_std_exit_pressure |
| What counts toward exit pressure? | Exits and the resolution fee curve | GET /v1/exit-pressure/history, 1s_std_exit_pressure |
| What backs STANDARD, and how is POL different from vault ETH? | Reserves, vaults, POL, and buybacks | GET /v1/backing/current, 1s_std_backing |
| When does a buyback actually fire? | Reserves, vaults, POL, and buybacks | GET /v1/buybacks/readiness, 1s_std_buyback_readiness |
| Why does my swap get taxed, and how much? | Trading tax hook | GET /v1/tax/schedule, 1s_std_tax_schedule |
| Is this contract address actually part of The Standard Reserve? | Contracts and addresses | GET /v1/addresses, 1s_std_addresses |
| What can governance change, and has anything one-way already happened? | Governance switches and risks | GET /v1/governance/changes, 1s_std_governance_changes |
| What are the actual risks / unresolved mechanics right now? | Governance switches and risks | n/a (documentation only; no single route summarizes this) |
| How dormant can a charter get before someone can claim it? | Deciding with the data | GET /v1/dormancy/bounties, 1s_std_dormancy_bounties |
Reading the answer, not just finding it
Every route above returns fields labeled with basis, serving_state, and (where relevant) assumptions[] or _source/_basis siblings. Read How to read a TSR response once before trusting a number pulled from any of them. A basis: inferred_from_bytecode field is real, deployed-contract behavior, but pinned without a verified source file; a measured field came straight off a chain call or log. Neither is "wrong" to use, but they're different strengths of claim, and conflating them is the single easiest way to overstate what this API actually knows.