Glossary

Two kinds of term are mixed together below: general vocabulary, and words that mean something particular at VerveContext. Where the two differ, the VerveContext meaning is the one stated.

A

API key — the credential identifying your account. It is a bearer credential: whoever holds it can spend your credits. See authentication.

Authentication — proving who you are. Here that is the API key, and nothing else.

Authorization — what you are allowed to do once identified. Determined by your plan and by any restrictions on the key. Worth keeping distinct from authentication: the two fail for different reasons and are fixed in different places.

B

Billing cycle — the month your allowance is counted over. It runs from your signup date on the free plan and from your subscription date on a paid one, not from the first of the month.

C

Concurrency — how many of your requests may be in flight at the same moment. A separate limit from the per-minute rate; see rate limits.

Client — the application hosting the agent: Claude, Cursor, VS Code, or anything else that speaks MCP. It owns the connection; your agent calls through it.

Credit — the unit of usage. Most calls cost one credit and some cost more; each reference page states its own. Failed calls are not billed.

D

Dashboard — dashboard.vervecontext.com, where keys, usage and billing live.

Deprecation — announcing that something will be removed while it still works. Deprecated things keep functioning until a stated date.

E

Error handling — deciding what happens on each failure. The distinction that matters is which failures are worth retrying and which are identical on the next attempt. See errors.

F–G

Free plan — a real plan that renews monthly, not a trial that expires. It is also the test environment, since every source behaves identically on every plan.

H

HTTPS — HTTP over TLS. Every call made on your behalf uses it; nothing travels in the clear.

I–J

Idempotent — safe to repeat with the same result. The lookups here are, in the sense that repeating one returns the same answer — but each repeat still costs a credit, so idempotent does not mean free.

L–M

Latency — how long a call takes. Varies by source — a lookup answers far faster than something that renders a page — and each reference page shows its own typical figure.

MCP (Model Context Protocol) — the standard by which a client discovers and calls external tools on a model's behalf. See MCP server.

O–P

OAuth — a framework for delegated access. You sign in once and the client holds a token, so no key is written into a config file or a workbook.

Parameter — an input a source needs, required or optional. The reference page for each source lists them with types and constraints.

Plan — your subscription level. It sets your monthly allowance, rate limit, concurrency and which features are available:

Premium field — a response field included on higher plans. Premium fields are absent rather than null on plans without them.

Primary key — the account's main API key, as distinct from a sub-key.

Q–R

Quota — your monthly credit allowance. Exhausting it looks like a rate limit and is not one; see rate limits.

Rate limit — the ceiling on calls per minute, set by your plan. Distinct from your quota: the rate limit resets every minute, the quota every billing cycle. See rate limits.

Reference page — the per-source page carrying parameters, response fields, credit cost, latency and examples. The authoritative description of any source.

Rotation — replacing your API key with a new one. Instant, with no grace period, so every system holding the old key stops working at once. See key rotation.

S

Schema — the formal description of a source's inputs and outputs. What the platform validates against, and what everything generated — reference pages, tool definitions, argument autocomplete — is generated from.

Source — one thing an agent can read from, exposed as a single tool. It has its own input schema, output schema, credit cost and reference page.

structuredContent — the response object a tool result carries alongside its text block, on protocol 2025-06-18 and newer. The parseable half; read it rather than the prose.

Sub-key — an additional credential billing to the same account, individually scopable and revocable. The right credential for a per-environment, per-client or per-agent integration. See sub-keys.

T–U

Throttling — limiting call rate to protect a service. When you are throttled, waiting is the whole fix.

Tool — how a source appears to an agent: a name, a description carrying its credit cost, an input schema and an output schema. Generated from the catalog, so a new source is a new tool the day it ships.

TLS — the encryption underneath HTTPS. All traffic uses it.

V–X

Versioning — keeping old behaviour working while new behaviour ships.

Workspace — one account's view of the dashboard. You always have your own, and joining a team gives you access to theirs. See workspaces.

Next

Quickstart puts most of these into one working example, and the FAQ answers the questions that come after it.