Skip to content
Gungner docs

Getting access

Where to send requests

Section titled “Where to send requests”

Gungner runs one environment today: production. Requests made with the credentials Gungner issues you are live requests against it.

  • API origin: https://api.gungner.ai
  • Portal origin: https://portal.gungner.ai
  • MCP: the same API origin, at /mcp — MCP isn’t a separate server or a different host, it’s the same process as the REST API.

What each route returns today, by country, is in the country coverage matrix: some data is live, some is built but gated, some is planned.

Getting credentials

Section titled “Getting credentials”

Credentials are issued by Gungner on request: send Gungner a short request and you receive a client_id and client_secret.

Test-mode keys, which would let you build and test an integration without touching live data, are planned. There is no date for them yet.

Walking it end to end

Section titled “Walking it end to end”

1. Mint a token.

Terminal window
curl -s -X POST https://api.gungner.ai/oauth/token \
  -H 'content-type: application/json' \
  -d '{
    "grant_type": "client_credentials",
    "client_id": "YOUR_CLIENT_ID",
    "client_secret": "YOUR_CLIENT_SECRET"
  }'

2. Make one call. Look up a Swedish company by its organisation number:

Terminal window
curl -s https://api.gungner.ai/v1/companies/YOUR_ORGNR \
  -H "authorization: Bearer YOUR_ACCESS_TOKEN"

3. Try it over MCP instead. Same bearer token, same data, different transport — POST to https://api.gungner.ai/mcp. See Using the MCP server for the full request shape and a worked example.

That’s the whole loop: token, REST call, MCP call, all against the same credentials and the same tenant.

What’s next

Section titled “What’s next”