Skip to content
One API · InfobelPRO

European company data through one API

VAT verification, firmographics and company financials behind a single key, one schema, and a schema-identical sandbox. Stop stitching vendors together.

stargate.infobelpro.com
curl "https://stargate.infobelpro.com/vatsearch/v1/verify?vat_number=BE0453834657" \
  -H "Authorization: Bearer ifp_live_your_key"
X-Stargate-Credits-Used: 1

Speaks the standards your systems already use

  • ISO-3166
  • NACE Rev. 2
  • VAT / VIES
  • REST / JSON
Why a gateway

One integration instead of many

Company data usually means a different vendor, key and schema for every field. Stargate collapses that into a single, consistent surface.

The old way

  • A different vendor, contract and SDK for every dataset
  • A separate API key and auth scheme to rotate for each
  • Inconsistent schemas you normalise yourself
  • Opaque monthly quotas and surprise overages

The Stargate way

  • VAT, firmographics and financials behind one gateway
  • One Bearer token, one field-filtered schema
  • A schema-identical sandbox for zero-risk onboarding
  • Prepaid credits you can see draining in every response
How it works

From zero to integrated in three steps

  1. 1

    Get a key

    Start in the sandbox with a test key, then contact sales for a production key scoped to your bundle.

  2. 2

    Call the API

    One Bearer token, stable product paths, and the same request shape in sandbox and production.

  3. 3

    Get field-filtered JSON

    Responses are filtered to your entitlements, with your credit balance returned in the headers.

  • 3 Unified products
  • 5 API endpoints
  • 1 Key, token & schema
  • 2 Schema-identical environments
Developer-first

Call it the way you already work

Bearer auth, predictable paths, and identical requests in sandbox and production. Copy, paste, ship.

Quickstart
curl "https://stargate.infobelpro.com/vatsearch/v1/verify?vat_number=BE0453834657" \
  -H "Authorization: Bearer ifp_live_your_key"
Response
{
  "data": {
    "country": "BE",
    "vat": "BE0453834657",
    "valid": true,
    "company": {
      "name": "ACME EUROPE SA",
      "registration_number": "0453834657",
      "address": {
        "street": "Rue de l'Industrie 12",
        "postal_code": "1000",
        "city": "Bruxelles",
        "country": "BE"
      }
    }
  },
  "request_id": "b3f1c2a8-..."
}
X-Stargate-Credits-Used: 1
Where Stargate fits

Built for teams tired of gluing data vendors together

How the Stargate gateway compares to stitching multiple vendors together, across five capabilities.
Capability Multiple vendorsStargate gateway
Integrations One per dataset One gateway
Authentication A key and scheme each One Bearer token
Schema Normalise yourself One field-filtered schema
Onboarding Varies by vendor Schema-identical sandbox
Billing visibility Opaque quotas, overages Prepaid credits, per response
Standards & identifiers

Interoperable by default

Stargate returns the identifiers and classifications your warehouse, CRM and compliance tooling already understand.

  • ISO-3166

    Country codes on every record, ready to join.

  • NACE Rev. 2

    EU sector classification, no custom mapping.

  • VAT / VIES

    Validated against the EU VIES registry.

  • REST / JSON

    Predictable paths and field-filtered JSON.

Simple, prepaid pricing

Buy credits once. They never expire.

Stargate bills on prepaid lifetime credits — not monthly subscriptions. Every billable request decrements your balance, credits never reset, and you only pay for what you use.

See how pricing works

One key, one schema, and entitlements frozen to your key — so your integration doesn’t change when the data behind it does. Build against a schema-identical sandbox, then flip to production with the same code.

Start building in the sandbox today

Schema-identical responses mean the code you write against the sandbox is the code you ship.