Skip to main content
The same rules apply whether you use Glasser through an Agent, MCP, the CLI, or HTTP.

​
From request to data

Glasser connects you to paid data from specialist Providers. An Endpoint is one Provider operation, with its own input schema, version, and Price. Your Glasser Key gives you access without separate Provider accounts.
  1. Search for an Endpoint that fits your request.
  2. Inspect its input schema and current Price.
  3. Run it to retrieve data. Glasser records the result and charge in a Run.
Search and Inspect are free. For predefined tasks, Solutions can select an Endpoint and map your input for you. Both paths use the same Runs and Workspace balance.

​
Understand the Price

Inspect shows how an Endpoint charges:
  • Successful result: a flat amount, or a metered amount (such as per result or token) with a cap.
  • Other outcomes: separate rules for no result, Provider errors, timeouts, and internal failures (NO_RESULT, PROVIDER_ERROR, TIMED_OUT, INTERNAL).
A new Run uses the Price at admission and keeps it through settlement. An Endpoint version does not lock the Price for future Runs. Amounts are exact USD decimal strings, such as "0.005". Use decimal arithmetic, not floating-point arithmetic, when adding them.

​
Run status

Before creating a Run, Glasser checks access and available funds, then places a Hold for the maximum charge. A refused request creates no Run and no charge. When the Run finishes, Glasser closes the Hold and records the final charge. A stop request after dispatch does not cancel the Provider’s work. Read the returned status and final charge; see Stop a Run.

​
Read the result and charge

Check these fields separately:

​
Retry without a second charge

After a timeout or lost connection, retry with the same idempotency key to retrieve the original Run without starting or charging for another one.
  • Keep provider, endpoint, input, and endpoint_version the same.
  • Changing those execution parameters with the same key returns a conflict.
  • Use a new key only when you intend to start another Run.
Changing task_id or metadata does not create a new Run or update the original Run. MCP responses also include replayed: true for a retry; HTTP API and CLI responses return the Run without this field.

​
Keys and policy

A Key belongs to a Workspace. Runs use that Workspace’s balance. An Endpoint must be allowed by both the Workspace’s Policy and the Key’s Policy. Search omits Endpoints outside that access; Inspect returns not-found for them.

​
Adding funds

Add funds on the Balance page. The API, CLI, and MCP cannot add funds. A Grant is free balance: it does not expire and spends like any other balance. Every new Workspace starts with a signup Grant. Referral and share Grants have lifetime limits per Workspace; the console shows the current amounts and limits. Grants appear in the balance history with kind grant.

​
One model, four surfaces

The same execution, billing, and policy rules apply to the HTTP API, the CLI, the MCP server, and the agent Skill.