How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
IBANforge

IBANforge API Keys API

API key management — generate free keys and check usage

Documentation Provider Profile APIs.io OpenAPI GitHub

IBANforge API Keys API is one of 9 APIs that IBANforge publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include APIKeys. The published artifact set on APIs.io includes an OpenAPI specification and 1 JSON Schema.

This API exposes 13 operations across 13 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.8.0.

Requests are made against 2 base URLs: https://api.ibanforge.com, http://localhost:3000.

13 operations 13 paths 2 schemas 4 GET9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.8.0
Base URL
https://api.ibanforge.com
Authentication
API Key, HTTP Bearer, API Key
Contact
IBANforge support
Resource Areas
1

Authentication & Security 3

IBANforge API Keys API declares 3 security schemes for authenticating requests. An API key is passed in the header as PAYMENT-SIGNATURE (x402Payment). It accepts HTTP bearer tokens (apiKey). An API key is passed in the cookie as ibanforge_account (accountSession).

  • x402Payment — x402 USDC micropayment signature (protocol v2). Clients holding v1 payment requirements may send the same signature as X-Payment; both are accepted.
  • apiKey — API key (Bearer ifkxxx) — 25 free requests/month without an email address, 200 a month once claimed, or a custom quota for paid keys
  • accountSession — Session of the account page, set by POST /v1/account/session: HttpOnly, Secure, SameSite=Strict, Path=/v1/account, 7 days from sign-in. Read-only: it opens no…

Paths & Operations 13

Across 13 paths, the API surfaces 13 operations — 4 GET, 9 POST. Each is listed below with its method, path, parameters, and response codes.

API Keys 13

API key management — mint a key with or without an email address, claim it, rotate it, check its usage

POST
/v1/keys/generate
Generate a free API key
generateApiKey body → 201400403409413429503
POST
/v1/keys/device
Open a device authorization request (RFC 8628)
openDeviceGrant body → 201400413429503
POST
/v1/keys/device/token
Collect the key once a human has approved (long-polling)
collectDeviceGrantKey body → 200400413429
POST
/v1/keys/device/lookup
Read a pending device request, and take its approval token
lookupDeviceGrant body → 200400404413429
POST
/v1/keys/device/approve
Approve a device request and mint the key
approveDeviceGrant body → 200202400403404409413415
POST
/v1/keys/device/deny
Refuse a device request
denyDeviceGrant body → 200400403404413415429
GET
/v1/keys/usage
Check API key usage
getApiKeyUsage → 200401429
GET
/v1/keys/report
Read everything this key did
getApiKeyReport 1 param → 200401429
POST
/v1/keys/revoke
Revoke the presented API key
revokeApiKey → 200401404429
POST
/v1/keys/claim
Raise the presented anonymous key to the free tier
claimApiKey body → 200202400401403409413429
POST
/v1/keys/rotate
Replace the presented API key with a fresh one
rotateApiKey → 201401404429
GET
/stats
Detailed statistics
getStats → 200403429
GET
/stats/history
Historical statistics
getStatsHistory 1 param → 200400403429

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are StatsOverview (7 properties), ApiError (2 properties). Each schema is shown below with its type and property counts.

StatsOverview
object
7 properties 5 required
ApiError
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ibanforge-api-keys-api-openapi.yml Raw ↑

Other APIs IBANforge publishes across the network.

IBANforge BIC API
AE Profile APIs.io
IBANforge Compliance API
AE Profile APIs.io
IBANforge Credits API
AE Profile APIs.io
IBANforge Free API
AE Profile APIs.io
IBANforge IBAN API
AE Profile APIs.io
IBANforge MCP API
AE Profile APIs.io
IBANforge Swiss Clearing API
AE Profile APIs.io
IBANforge Account API
AE Profile APIs.io
#APIKeys
← Back to I APIs
API Details
ID
ibanforge:ibanforge-api-keys-api
Base URL
https://api.ibanforge.com
Docs
https://api.ibanforge.com
Provider
IBANforge
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=ibanforge-api-keys-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/ibanforge-api-keys-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of IBANforge API Keys API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.