Skip to main content
Pull endpoints and watch poll ticks deduct credits from your Account balance. Insufficient credits return HTTP 402 with code: "INSUFFICIENT_CREDITS". Check your balance anytime (free):

​
Where credits come from

One balance, funded from three places:
  • Free monthly credits — a Free Account’s allowance is set to 1,000 credits every 30 days, starting at sign-in. Unused free credits do not roll over; the next cycle sets the allowance back to 1,000.
  • Plan allowance — each paid cycle grants your plan’s monthly credits (Solo 150k, Growth 650k, Pro 2.5M) instead of the free cycle. Credits are the meter, not the product: a plan sells queries, terms and freshness, and includes far more credits than a monitoring account spends (see Limits).
  • Credit packs — one-off top-ups from the dashboard, at a flat rate regardless of plan. Packs never expire and add on top of any allowance.
Your balance never goes negative, and a tick that could not be debited is not metered. Packs raise your balance but never your request quota or Watch caps — those move only with the plan. See Limits.

​
Reading your mentions

Free. GET /v1/mentions, GET /v1/queries, GET /v1/queries/{id}, GET /v1/queries/{id}/results and GET /v1/queries/{id}/buckets read data you already paid to collect — reading it back is the product, not a metered act. Creating, editing, pausing and resuming queries is free too; what costs is the polling those queries do (Watch billing). One exception. Adding mode=semantic to /v1/mentions or /v1/queries/{id}/results searches by meaning rather than by substring, which calls an embedding provider and is charged at the AI rates below. It is never the default and never inferred: leave the parameter out and the read is a free substring scan. The charge is cached for ten minutes, so re-asking the same question inside that window costs nothing — the same terms an API key gets and a dashboard session gets, deliberately.

​
AI answers rates

The only three-figure rate in this table, and the reason is that a run is a real purchase rather than a public endpoint: asking an answer engine costs money per question. Two engines every six hours is 800 credits a day. An engine that errors is not charged. The others still answer, and a failed engine keeps its previous answer as the baseline. There is no pull endpoint for this Source — see AI answers.

​
Vinted analytics rates

Nephia’s own price observations, read back. Not a call to Vinted.

​
Watch billing

Each active watch poll tick deducts credits at the source search rate: 4 credits for X, Reddit, and Vinted — 8 for a Reddit watch in types: all, which reads two listings per tick; 5 credits for Youtube; 1 credit for Bluesky, Hacker News and RSS — an RSS tick that gets a 304 is charged too, because the poll happened. AI answers is billed differently: 100 credits per engine per run, because a run is a purchase rather than a fetch (see AI answers rates). If your balance is too low, the watch is paused with pausedReason: insufficient_credits and webhook delivery stops until you top up and resume manually. Watch management endpoints (list, get, pause, resume, delete, events, activity) do not charge credits. Webhook delivery itself does not add a separate per-event credit charge beyond the poll tick. A watch created with an agent step charges its step on top of the tick, at the AI rate below — one credit per 25 events read.

​
In the dashboard

The dashboard spends the same balance as the API, and most of what it spends is polling: a query’s watches, billed per tick at the rates in Watch billing. Everything below is the other kind, a charge you make by clicking something. The screen names a price only when it is at least 1% of your monthly allowance. A click worth a hundredth of your month is a decision the button can help you make; a click worth a thousandth is noise on every control you own. So the number lives here, and every charge, including the quiet ones, is on your account’s Spend statement, named after the action that made it and filterable by day. What that means in practice: on a plan with a 150,000-credit cycle none of the rates above reaches the threshold and no button quotes a figure. On a 1,000-credit free cycle, “Suggest prompts” and “Read my site” do, and they say so. Standing costs are the exception and are always stated, whatever they come to: a query that polls, a followed account, an answer-engine prompt. Those are written as a share of your month, “about 14% of your month at this interval”, because what matters about a subscription is not what one tick costs but what the month does.

​
AI rates

Billed per batch, after a valid answer: a batch the provider could not answer is not charged, and meta.credits_used reports what actually was. See AI.