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

Worthune API

Worthune API as documented publicly: 22 operations. Contract generated from the documentation by API Evangelist (2026-10-19); not the provider's own document.

Worthune API is published by Worthune on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

The published artifact set on APIs.io includes an OpenAPI specification and 4 JSON Schemas.

This API exposes 22 operations across 19 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 2026-10-19.

22 operations 19 paths 4 schemas 8 GET14 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2026-10-19
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Worthune API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearer). By default, every request must be authenticated.

Paths & Operations 22

Across 19 paths, the API surfaces 22 operations — 8 GET, 14 POST. Each is listed below with its method, path, parameters, and response codes.

Api 22
POST
/api/v1/book-scan
POST /api/v1/book-scan — the same coordination sweep across up to 250 households at once
post_api_v1_book_scan → 201
GET
/api/v1/decisions/{id}
GET /api/v1/decisions/{id}
get_api_v1_decisions_id 1 param → 200
POST
/api/v1/embed-tokens
POST /api/v1/embed-tokens — mints a short‑lived, household‑scoped signed token
post_api_v1_embed_tokens → 201
GET
/api/v1/evals/refinance
GET /api/v1/evals/refinance
get_api_v1_evals_refinance → 200
POST
/api/v1/grade/{model}
Worthune Evals — Ground Truth for Financial AI
post_api_v1_grade_model 1 param → 201
POST
/api/v1/households
POST /api/v1/households — create the document (pass your own importKey and a retried create returns the household it already made)
post_api_v1_households → 201
POST
/api/v1/households/import
POST /api/v1/households/import — bulk migration, up to 200 households a batch
post_api_v1_households_import → 201
POST
/api/v1/households/{id}/decisions
Each strategy returns ranked alternatives with a computed dollar delta against the baseline — every option shown, never just a winner — and each decision carries its own evidence record.
post_api_v1_households_id_decisions 1 param body → 201
POST
/api/v1/households/{id}/project
Run this yourself
post_api_v1_households_id_project 1 param → 201
GET
/api/v1/models
Discover models at GET /api/v1/models
get_api_v1_models → 200
GET
/api/v1/models/{model}
Three endpoints per model: the JSON contract ( GET /api/v1/models/{model} )
get_api_v1_models_model 1 param → 200
POST
/api/v1/models/{model}
Three endpoints per model: execution ( POST /api/v1/models/{model} )
post_api_v1_models_model 1 param → 201
POST
/api/v1/models/{model}/report
POST /api/v1/models/{model}/report takes the same JSON inputs as a run and returns a print‑ready HTML document
post_api_v1_models_model_report 1 param → 201
GET
/api/v1/openapi.json
The whole surface is described by GET /api/v1/openapi.json
get_api_v1_openapi_json → 200
GET
/api/v1/project
Run the Engine on Your Own Numbers — No Signup, Nothing Stored
get_api_v1_project → 200
POST
/api/v1/project
POST /api/v1/project — the full projection and optional Monte Carlo on a household document you send
post_api_v1_project → 201
GET
/api/v1/project/examples/retired-couple-spousal
Run the Engine on Your Own Numbers — No Signup, Nothing Stored
get_api_v1_project_examples_retired_couple_spousal → 200
POST
/api/v1/project/examples/retired-couple-spousal
POST /api/v1/project/examples/retired-couple-spousal
post_api_v1_project_examples_retired_couple_spousal → 201
POST
/api/v1/records/verify
POST /api/v1/records/verify — verify a decision record’s digest
post_api_v1_records_verify → 201
GET
/api/v1/telemetry
63 models in the catalog today.
get_api_v1_telemetry → 200
POST
/api/v1/verify
Documents A run you can hand to a reviewer
post_api_v1_verify → 201
POST
/api/v1/verify/emergency-fund
POST /api/v1/verify/emergency-fund
post_api_v1_verify_emergency_fund body → 201

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are PostApiV1VerifyEmergencyFundRequest (2 properties), GetApiV1ProjectExamplesRetiredCoupleSpousalResponse (1 property), GetApiV1ProjectResponse (1 property), PostApiV1HouseholdsIdDecisionsRequest (1 property). Each schema is shown below with its type and property counts.

PostApiV1HouseholdsIdDecisionsRequest
object
1 property 1 required
GetApiV1ProjectResponse
object
1 property
GetApiV1ProjectExamplesRetiredCoupleSpousalResponse
object
1 property
PostApiV1VerifyEmergencyFundRequest
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

worthune-openapi-generated.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Worthune 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.