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

Lucid Embedding Utils API

Create, retrieve, delete, and change the version of embed instances on a document.

Lucid Embedding Utils API is one of 37 APIs that Lucid publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Embedding Utils. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.lucid.co.

5 operations 4 paths 2 schemas 1 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.lucid.co
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Lucid Embedding Utils API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 142 scopes. It accepts HTTP bearer tokens (ApiKey).

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Embedding Utils 5

Create, retrieve, delete, and change the version of embed instances on a document.

GET
/v1/documents/{documentId}/embeds/{embedId}
Get Document Embed
getEmbedInformation 2 params → 200403
DELETE
/v1/documents/{documentId}/embeds/{embedId}
Delete Document Embed
deleteEmbed 2 params → 204403
GET
/v1/documents/{documentId}/embeds/{embedId}/document
Get Document Embed Document
getEmbedDocument 2 params → 200403
POST
/v1/documents/{id}/embeds
Create Document Embed
createEmbed 1 param body → 201400403
POST
/v1/documents/{documentId}/embeds/{embedId}/changeVersion
Change Document Embed Version
changeEmbedVersion 2 params body → 200400403

Schemas 2

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

EmbedInformation
object
Information about the requested Embed.
5 properties
EmbedDocument
object
Information about the docuement correlated to the requested Embed.
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lucid-embedding-utils-api-openapi.yml Raw ↑

Other APIs Lucid publishes across the network.

Lucid MCP Server
Lucid Accounts API
Lucid Audit Logs API
Lucid Cloud API
Lucid Collection API
Lucid Collection Properties API
Lucid Create Diagram API
Lucid Data Item API
Lucid Data Set API
Lucid Data Set Grant API
Lucid Data Set Properties API
Lucid Data Source API
Where this information came from

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