Back
⚡ API

API Terms of Service

Last updated March 2026

Built for builders

These terms cover your use of the btob.dev API. We’ve kept them short and human on purpose. By using an API key, you agree to these terms. If anything is unclear, just email us — we’d rather talk it through than hide behind legalese.

What this covers

These terms apply to all access to the btob.dev API — including the REST API, the MCP server, and any programmatic access using an API key. They apply whether you’re building a prototype, a production product, or running one-off data queries.

Acceptable use

Use the API for legitimate business purposes. Building products on top of our data is fine — and encouraged. That’s exactly why this API exists.

  • ✓Build search tools, lead enrichment flows, procurement pipelines, agent integrations.
  • ✓Use our data as a layer in your product — that’s the whole point.
  • ✗Don’t redistribute bulk data or resell raw database dumps. You’re licensing access, not buying the database.
  • ✗Don’t use the API to build a competing data service that re-exports our records at scale.
  • ✗Don’t scrape, mirror, or systematically harvest the full dataset via the API.

If your use case is in a grey area, just ask. We’d rather say yes with context than have you guess.

Rate limits

The default limit is 60 requests per minute per API key. This is enough for most use cases, including real-time search and agent workflows.

If you need more — for bulk enrichment, large-scale pipelines, or enterprise use — just contact us at [email protected]. We’ll sort it out.

Attribution

When displaying btob.dev data directly to end users in your product, include a short attribution:

Data provided by btob.dev

This doesn’t apply to internal tools, analytics pipelines, or cases where the data is processed before presentation. Just use your judgment — if a user would wonder where the data came from, a small credit is the right move.

Data accuracy

We source from official government registries across Europe — the same records that companies file with their national authorities. That means the data is as accurate as the source.

Data is provided as-is. We continuously improve coverage, freshness, and accuracy, but we can’t guarantee that every record is up to date at any given moment. Don’t use this data as the sole basis for high-stakes decisions without independent verification.

API key security

Your API key is your credential. Keep it confidential.

  • ✗Don’t expose your key in client-side code (JavaScript bundles, browser requests).
  • ✗Don’t commit it to public repositories — even in example configs or env files.
  • ✗Don’t pass it in URLs as a query parameter (use the Authorization header instead).

If you think your key has been compromised, contact us immediately at [email protected] and we’ll rotate it right away. No questions asked.

Changes to these terms

We may update these terms as the API evolves. For minor changes, we’ll update this page. For anything material — new restrictions, pricing changes, significant policy shifts — we’ll notify you by email in advance. If you’ve used the API once, you’ll hear from us before anything important changes.

Questions? Just ask.

If anything here is unclear, if you have a use case you want to check, or if something doesn’t feel right — email [email protected]. We’re a small team and we respond within 2 working days. No forms, no tickets, no runaround.