Properties
| Name | Type | Description |
|---|---|---|
| user_identifier | string | User identifier (REQUIRED) |
| verification_id | string | Verification ID from a previous verification. (REQUIRED) Must exist in identity_verifications table and belong to the user associated with the organisation. |
| sign_with | array | Optional context fields to bind into the enclave signature. public_key is always signed implicitly and must not be included. Every requested field must resolve to a non-empty value, except key_fingerp |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/coincover/main/json-schema/coincover-key-generate-request-schema.json",
"title": "KeyGenerateRequest",
"x-generated": "2026-10-09",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/_original/coincover-retail-openapi-openapi.json#/components/schemas/KeyGenerateRequest",
"type": "object",
"properties": {
"user_identifier": {
"type": "string",
"description": "User identifier (REQUIRED)"
},
"verification_id": {
"type": "string",
"description": "Verification ID from a previous verification. (REQUIRED) Must exist in identity_verifications table and belong to the user associated with the organisation."
},
"sign_with": {
"type": "array",
"description": "Optional context fields to bind into the enclave signature. public_key is always signed implicitly and must not be included. Every requested field must resolve to a non-empty value, except key_fingerprint which may resolve after generation. Each field may only be listed once.",
"items": {
"type": "string",
"enum": [
"external_customer_id",
"external_package_id",
"pulled_by_id",
"pulled_by_type",
"user_id",
"key_id",
"key_fingerprint"
]
}
}
},
"required": [
"user_identifier",
"verification_id"
]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/coincover-key-generate-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.