Artificial Intelligence

x-tool-description

`x-tool-description` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Retrieves paginated active deals with filtering by owner, person, organization, `, `Creates new sales deals with customizable properties: title (required), value, p`, `Retrieves paginated archived deals with same filtering as active deals. Essentia`, `Soft-deletes deals with 30-day recovery period before permanent removal. Essenti`. Consistent with artificial intelligence — this is inferred from where the key appears and what it carries, not from any published definition.

Artificial Intelligence derived description
How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.
27 occurrences
1 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 27

What its value looks like

Value shapeOccurrences
string27

Observed values

Sampled from the specifications, most frequent first.

Retrieves paginated active deals with filtering by owner, person, organization, Creates new sales deals with customizable properties: title (required), value, pRetrieves paginated archived deals with same filtering as active deals. EssentiaSoft-deletes deals with 30-day recovery period before permanent removal. EssentiFetches comprehensive details of a specific deal by ID, including all propertiesModifies deal properties using PATCH semantics for partial updates without affecRetrieves users following a deal for visibility into collaboration and stakeholdAdds user as deal follower to receive notifications and updates about progress.

Providers publishing it

All 1.

pipedrive

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the artificial intelligence job.