Concepts

Product surfaces

Surface	Host	Audience
Site + docs	https://lybra.dev	Humans
REST API	https://api.lybra.dev	Developers
MCP	https://mcp.lybra.dev	Agents

Same Rascode API key and datasets.read scope work on REST and MCP. The seller brand is RASCODE; the product brand is Lybra. LEDES and UTBMS remain the industry standards behind the corpus.

Read-only vocabulary

v1 is reference lookup only: formats, error codes, timekeeper classifications, IPMM elements, and UTBMS tasks / activities / expenses. There is no write API for inventing or mutating industry codes.

A correct lookup does not guarantee that a particular e-billing portal will accept a given invoice. You (or your operator) own submission outcomes. See Terms.

JSON shape

Top-level envelope keys are snake_case (error_codes, code_sets, set_key). Resource fields are camelCase (formatKey, errorType).

The TypeScript SDK @rascode/lybra unwraps envelopes and returns camelCase resource objects.

Billable unit

One successful corpus read = 1 api_request:

• a 2xx GET on /v1/ledes/* or /v1/utbms/*, or
• one MCP tools/call that hits the same handlers

Auth failures and other 4xx responses do not consume quota. Docs and the marketing site are free.

Path prefixes

Prefix	Corpus
/v1/ledes/*	LOC LEDES formats, error codes, timekeepers, IPMM
/v1/utbms/*	ABA UTBMS code sets, tasks, activities, expenses

OpenAPI for this product slice: /openapi.json. Interactive listing: API reference.