Reverse: find the Keybase user behind an identity
API · /keybase-api
Keybase Identity API
healthy
4,778 Subscribers
Live cryptographic social-identity lookup from Keybase — no key, nothing cached. Keybase links a person's identities together with public-key cryptography, so this answers "who is this account, really, and what else are they?". The user endpoint takes a Keybase username and returns the profile (full name, location, bio, picture), every verified identity proof — the Twitter, GitHub, Reddit, Hacker News, Mastodon, website and DNS accounts that user has cryptographically proven are theirs — plus their on-file cryptocurrency addresses (Bitcoin, Zcash and more) and PGP key fingerprint: Keybase user "chris" resolves to Chris Coyne in Maine, with proven twitter/github/reddit @malgorithms and a Bitcoin address. The lookup endpoint runs the reverse — give it a GitHub, Twitter, Reddit or Hacker News handle, a domain or a PGP fingerprint and it finds the Keybase user who proved it, so a bare GitHub handle resolves to a full verified identity. The proofs endpoint returns just the connected-accounts graph and crypto addresses. This is the identity-verification and social-graph layer for any trust, onboarding, anti-impersonation, social or crypto app — proven links, not claimed ones. Live from Keybase, nothing stored. Distinct from single-platform profile APIs — this is the cross-platform proven-identity graph. 4 endpoints.
api.oanor.com/keybase-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 395 ms
- Server probes · 24h
- Subscribers
- 4,778
- active
- Total calls
- 95
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 13,000 calls / month
- 3 requests / second
- Hard cap (429 above quota, no overage)
- 13,000 calls/month
- 3 req/sec
- Profile, proofs & reverse lookup
- No credit card
Starter
€5.50 /month
- 160,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 160,000 calls/month
- 8 req/sec
- Verified accounts, crypto addresses, PGP
- Email support
Pro
€15.50 /month
- 680,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 680,000 calls/month
- 15 req/sec
- Trust, onboarding & anti-impersonation
- Priority support
Scale
€38.00 /month
- 3,400,000 calls / month
- 30 requests / second
- Hard cap (429 above quota, no overage)
- 3,400,000 calls/month
- 30 req/sec
- Identity-graph scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Matchain API
Live EVM on-chain data for Matchain (chain id 698) — the BNB-Chain-secured Layer-2 focused on decentralised identity and social, where gas is paid in BNB — served directly from the public Matchain JSON-RPC with server-side resilience. The status endpoint returns the chain and network id, the latest block height and the node client version. The block endpoint returns a block by number (or the latest) with its hash, parent hash, timestamp, transaction count, gas used and gas limit, miner and size. The gas endpoint returns the current gas price in both wei and gwei. The balance endpoint returns the BNB balance and outgoing transaction count for any address, converted from base wei (18 decimals) into whole BNB with exact big-integer scaling. Every figure is read live from the chain over JSON-RPC — nothing bundled or modelled — behind a short server-side cache with keep-warm so the feed stays fast and fresh. Ideal for explorers, wallet and dashboard tooling, gas trackers, address monitors and analytics apps across the Matchain identity and social ecosystem. Live keyless upstream. 5 endpoints.
api.oanor.com/matchain-api
cheqd Chain API
Real-time on-chain data for cheqd (chain-id cheqd-mainnet-1), a Cosmos-SDK Layer-1 purpose-built for decentralised identity, verifiable credentials and trust registries, with CHEQ as its native coin (base denom ncheq, 9 decimals), secured by delegated proof-of-stake. The status endpoint returns the chain id, latest block height and time, proposer and node application version so you can confirm the chain is live and producing blocks. The validators endpoint returns the full bonded validator set — each moniker, operator address, stake in CHEQ, commission rate and jailed flag — sorted by stake, plus the total bonded and not-bonded CHEQ. The supply endpoint returns the total CHEQ supply (in CHEQ and base ncheq), the bonded amount and the bonded ratio. The governance endpoint returns the most recent on-chain governance proposals with title, status and voting window. The meta endpoint documents the chain, denom and decimals. Reads a live cheqd Cosmos-SDK LCD node directly (with mirror fallback), so values are current to the latest block. Live, nothing stored. 5 endpoints. This serves chain-level staking, supply and governance data; for DID documents or credential resolution use a dedicated cheqd resolver API.
api.oanor.com/cheqd-api
Tezos Domains (.tez) API
Read the Tezos Domains naming service live from the public TzKT indexer — no key. Tezos Domains maps human-readable .tez names to Tezos addresses, the way ENS maps .eth names on Ethereum. None of the Tezos on-chain, governance, baker, smart-rollup or FA-token readers expose the naming layer; this opens it. Browse the most recently active .tez domains with their owner address, the address they point to, registration level and expiry; forward-resolve a .tez name to the address that owns it (how a wallet turns "alice.tez" into a tz1 address); and reverse-resolve any Tezos address to the .tez names registered to it (an address can own several). The identity / naming layer for Tezos wallets, explorers, payment UX and analytics. Distinct from the Tezos on-chain reader, the self-amending governance reader, the baker reader, the smart-rollup reader and the FA-token registry. Live from the indexer; short cache only.
api.oanor.com/tezosdomains-api
Email Normalize API
Canonicalize email addresses so you can deduplicate accounts and catch different aliases of the same inbox. The normalize endpoint lower-cases the address and applies provider-aware rules: it strips the dots from Gmail and Googlemail local parts (because Gmail ignores them) and maps googlemail.com to gmail.com, removes +tag sub-addressing for Gmail and the many providers that support it — Outlook, Hotmail, Live, iCloud, Fastmail, Proton, Yandex, Zoho, GMX and more — and, by default, for every domain so duplicates never slip through, while reporting exactly which changes it made and which provider it detected. The compare endpoint normalizes two addresses and tells you whether they resolve to the same mailbox. Everything is computed locally and deterministically, with no DNS or network calls, so it is instant and private. Ideal for sign-up and registration dedup, fraud and abuse prevention (one person, many aliases), CRM and mailing-list hygiene, and merging customer records. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This normalizes addresses for comparison; to verify that an address actually exists and can receive mail (MX, disposable, role accounts) use an email-verification API.
api.oanor.com/emailnormalize-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Keybase Identity API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Keybase Identity API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Keybase Identity API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Keybase Identity API cost?
Keybase Identity API has a free tier with 100 calls / month. Paid plans start at €5.50 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Keybase Identity API GDPR-compliant?
All requests to Keybase Identity API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/keybase-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/keybase-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/keybase-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);import requests
r = requests.get(
"https://api.oanor.com/keybase-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
📌 Pinned
🔒 Locked
·
·
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.