{"version":"2.1.248","anchor":"usage-lookups-can-skip-spend-computation","canonical_anchor":"usage-lookups-can-skip-spend-computation","heading":"Usage lookups can skip spend computation","tier":"internal","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/usage-lookups-can-skip-spend-computation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Usage lookups can skip spend computation\n\nUsage lookups can ask the server to skip computing spend.\n\n**What**\n\nThe usage fetch gained an at-wall mode that asks the server to skip computing spend, reported separately in telemetry.\n\n**Details**\n\n- Requests `\/api\/oauth\/usage?at_wall=1&skip_spend=1` and reports as `api_usage_fetch_at_wall` rather than `api_usage_fetch`.\n- Chosen by the caller; the plain endpoint and metric remain for everything else.\n\n**Evidence**\n\n`\/api\/oauth\/usage?at_wall=1&skip_spend=1`\n\n- Area: Usage & Limits\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}