gosset usage

How much of each corpus your account has been shown, and whether that is close to your plan's limit.

gosset usage

Unique records seen in the last 365 days

  assets          48 seen
  companies      180 seen
  deals          713 seen
  news           123 seen
  trials         550 seen

gosset usage --json     # the same report, machine-readable

What it counts

Distinct records, not requests. Asking for the same 200 drugs every morning is one number that stops growing; walking the corpus is one that doesn't. Rate limits already bound how fast you can ask; this bounds how much of the database an account ends up holding.

The window is a rolling 365 days, and a record counts once no matter how many times it comes back.

Limits

Coverage is capped as a share of each corpus, by plan. A percentage rather than a fixed number because the corpora differ by two orders of magnitude: 1% is 1,460 drugs but 10,210 news items.

There's also a floor, so a small corpus doesn't produce a punitive number: 1% of targets would be 88 records, which is an afternoon of ordinary browsing.

If you're near a limit, usage is where you see it before a query starts failing:

{
  "entity_type": "trials",
  "seen": 550,
  "limit": 4170,
  "over_quota": false,
  "window_days": 365
}

over_quota is the field to watch. limit: null means no cap applies to that entity for your plan.

If you're over

Requests for that entity are refused until the window rolls forward or the plan changes. Nothing else is affected: the quota is per entity, so exhausting trials leaves drugs working.

Narrowing your queries is usually the fix worth making anyway: --limit 500 pages through the corpus, whereas a filter answers the question.

# walks the corpus                     # answers the question
gosset trials --limit 500              gosset trials --drug tulisokibart --phase 3