Provided by Exa
Get the Body Text of Several Pages From Their URLs (Exa)
Get the body text of up to 10 documents from the urls already in hand: each delivered page comes back with its title, author, published date and its text, with an optional cap on characters. A URL that cannot be retrieved is reported on its own and is not charged. It reads the urls supplied to it — it does not find them.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"urls"
],
"properties": {
"urls": {
"type": "array",
"items": {
"type": "string",
"pattern": "^https?:\\/\\/",
"maxLength": 2048,
"minLength": 8
},
"maxItems": 10,
"minItems": 1
},
"maxAgeHours": {
"type": "integer",
"maximum": 720,
"minimum": -1
},
"maxCharacters": {
"type": "integer",
"maximum": 10000,
"minimum": 1
},
"livecrawlTimeout": {
"type": "integer",
"maximum": 12000,
"minimum": 1000
}
},
"additionalProperties": false
}{
"urls": [
"https://en.wikipedia.org/wiki/Battery_recycling"
],
"maxCharacters": 2000
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How to run it
Two fields identify it: the Provider and the endpoint key. The key looks like a path because it usually mirrors the Provider's own, but it is an opaque identifier — not a URL you can open. The same provider:endpoint pair is what your Policy lists.
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.mdThen ask for this Endpoint:
Run the Exa Endpoint /contents on Glasser with input {"urls":["https://en.wikipedia.org/wiki/Battery_recycling"],"maxCharacters":2000}glasser run -p exa -e '/contents' -i '{"urls":["https://en.wikipedia.org/wiki/Battery_recycling"],"maxCharacters":2000}' --endpoint-version 1Pinned to version 1, the one this page shows: if a newer version is published first, the Run is refused instead of charged under new terms. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"exa","endpoint":"/contents","input":{"urls":["https://en.wikipedia.org/wiki/Battery_recycling"],"maxCharacters":2000},"endpoint_version":1}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Pinned to version 1 for the same reason as the CLI.
What each outcome charges
| No result | The Provider answered: nothing matched. | $0.00 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The deadline won. | $0.00 |
| Internal failure | Our defect. | $0.00 |