Service metadata

Codefragmenten

curl "https://api.oanor.com/keybase-api/v1/meta" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/keybase-api/v1/meta", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/keybase-api/v1/meta");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/keybase-api/v1/meta",
    headers={"x-oanor-key": "oanor_test_..."}
)

Voorbeeldrespons

Een echte respons van dit endpoint, vastgelegd bij de laatste health check.

{
    "data": {
        "source": "Keybase public API (live)",
        "service": "keybase-api",
        "endpoints": {
            "GET /v1/meta": "This document.",
            "GET /v1/user": "A Keybase user's full identity (username=chris): profile, proofs, crypto addresses, PGP.",
            "GET /v1/lookup": "Reverse: find the Keybase user behind an identity (network=github&value=malgorithms, or github=malgorithms). Networks: twitter, github, reddit, hackernews, mastodon, domain, pgp.",
            "GET /v1/proofs": "Just the connected-accounts graph + crypto addresses (username=chris)."
        },
        "description": "Live cryptographic social-identity lookup from Keybase: a username resolves to its profile (full name, location, bio, picture), every verified identity proof (Twitter, GitHub, Reddit, Hacker News, Mastodon, website, DNS), cryptocurrency addresses and PGP fingerprint. Reverse-lookup finds the Keybase user behind a GitHub/Twitter/Reddit/Hacker-News handle, a domain or a PGP fingerprint. Live, no key, nothing stored. Distinct from single-platform profile APIs — this is the cross-platform proven-identity graph.",
        "upstream_status": "ok"
    },
    "meta": {
        "timestamp": "2026-06-09T11:39:56.894Z",
        "request_id": "d75431b7-4636-46a9-8daa-13c5b4e16a95"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}