Quickstart
Create a project, enable a product, mint a key, and make your first metered call.
Five steps, all in the console.
1. Create a project
A project is the boundary for everything — enabled products, keys, and usage. The console prompts you to create one the first time you sign in.
2. Enable a product
Open API catalog and enable Geo API, Parcels API, Inventory API, or AI API. A disabled product returns 403 product_not_enabled. AI additionally requires operator activation, a reviewed catalog and a linked USD billing account. See the AI quickstart.
3. Create a key
Open API keys → Create key. Pick scopes for what the caller
actually needs — geo:read and geo:resolve for Geo, parcels:read and
parcels:write for Parcels, inventory:read / inventory:write /
inventory:reserve for Inventory. Choose explicit scopes; for AI use ai:read and ai:generate.
The plaintext key is shown exactly once, at creation. The platform stores a hash — a lost key is replaced, never recovered.
Server-side only
Keep long-lived keys on your server. Never embed them in public browser or mobile bundles. The trusted Cloud playground accepts a pasted project credential temporarily in memory.
4. Make a call
curl "https://apis.cloud.feeef.org/v1/geo/states?country=DZ" \
-H "Authorization: Bearer $FEEEF_CLOUD_KEY"Or without an SDK, a bare fetch/http call works the same way — the SDKs
just add retries, idempotency, and typed errors on top:
const res = await fetch('https://apis.cloud.feeef.org/v1/geo/states?country=DZ', {
headers: { Authorization: `Bearer ${process.env.FEEEF_CLOUD_KEY}` },
})
const { data } = await res.json()5. Watch it land
Requests appear on the dashboard and against your key's quota within about a minute — metering flushes on a short delay, it is not instant.
Next
Authentication covers scopes and OAuth in full. Conventions covers the error envelope, pagination, and rate limits every endpoint shares.