Farbeam
Docs / Security and policy

Acceptable use

These rules keep a free service available for everyone. Enforcement is simple: limits, refused requests and revoked keys.

#You may

  • Build free or commercial products, bots, dashboards and research on the API.
  • Quote and republish data, as long as you state the limits and the time of the data.
  • Store rows for your own use after the 7-day retention.
  • Use one free key per service, up to 5 per account.
  • Credit Farbeam. This is welcome and not required.

#You may not

RuleReason or example
Avoid rate limits by rotating networks or keysLimits are shared across users. If you need more, write to us with your use case.
Create wallets or keys in bulk to get more unitsLimits are per key, and an account holds 5 active keys
Keep the maximum stream count open without readingConnections are limited to 6 per network and 400 in total
Probe or attack the service or its sourcesReport issues instead. See security.
Use the webhook system to send traffic to systems you do not controlA rule's URL must be yours or one you may use
Use the data to harass, threaten or identify private peopleIncludes linking a wallet to a named person from Farbeam output
Present data as a guarantee or as adviceFarbeam gives none. See the disclaimer.
Claim Farbeam endorses a token, project or personListing or labeling is not an endorsement
Imply a partnership or official linkFarbeam has announced no partners
Use Farbeam to support market manipulation, fraud or other illegal activityThis includes false claims built on selected rows
Resell raw API access as your own service with no added workBuild on the data, and do not proxy it

#Passing data on to your users

If your product shows Farbeam data, keep these facts visible:

  • Solana rows are samples. Keep the sampled flag.
  • Coverage is limited to curated tokens at $100,000 or more.
  • Labels are hand-curated and can be wrong or out of date.
  • unknown on a token check is not a pass.
  • USD values use a cached price when stored.

Do not remove these limits to make a result look more complete.

#How limits are enforced

SituationWhat happens
Over rate limit429 with Retry-After
Over daily limit429 daily_limit until 00:00 UTC
Too many streams429 with Retry-After: 30
A failing webhookThe rule turns off after 20 failed deliveries in a row
AbuseKeys may be revoked and access refused, with or without notice

Accounts hold a wallet address and no contact details, so there is no one to notify unless you wrote to us.

#No guarantee of service

The API can change or stop. Breaking changes follow versioning. No SLA exists today, and an SLA is Planned. Build fallback behavior into any system that depends on the API.

#Contact

Ask about a use case at contact@farbeamlabs.com or through @FarbeamX on X. Asking first is better than guessing, and it costs nothing.