Skip to main content
Make your first url2llm request with cURL or a direct HTTP call from Node.js or Python. Start with one public page, then choose the outputs your application needs.

1. Get an API key

Create an account, then open Dashboard > API keys. Signup automatically provisions your first organization. As an organization owner or admin, reveal an eligible active key or choose Create API key, give it a name, and copy the new secret. Dashboard-created keys have both scrape and map scopes. Set the key in the shell where you run the example:
Keep the secret in server-side configuration. API keys covers narrower scopes, live and test prefixes, reveal, rotation, and revocation.

2. Choose your client

cURL needs no additional package. The Node.js example uses built-in fetch; the Python example uses the standard library. No url2llm SDK installation is required for these examples. Run the saved example from the same shell where you set URL2LLM_API_KEY.

3. Send a scrape

This request fetches example.com and asks for Markdown and links. JavaScript rendering and main-content extraction are enabled by default.

4. Check the result

cURL prints the complete JSON response; the Node.js and Python examples print its Markdown and metadata. A successful response contains success: true and the page under data. This is an illustrative excerpt:
Check the API’s HTTP status and success before reading data. Then inspect metadata.status_code and a known heading or paragraph. The source status is separate from the API’s HTTP status. A source 404 can return a page result and is billable. Requested outputs appear in data; outputs you did not request are null. Page text and links depend on the source. There is no per-output success envelope or partial-result mode in the current API. Each ordinary scrape fetches fresh content and a billable request costs one credit. Supported extra formats have no current surcharge. Keep the top-level request_id for diagnosis and the source metadata beside content you store.

Try another operation

Map requires the map key scope. Scrape, branding, screenshots, and quote use scrape. Map returns candidates; select the URLs you need and scrape each one. It does not launch a managed crawl job.

If the request fails

For production retries, generate an Idempotency-Key once per distinct operation and reuse it with identical inputs. See retries and idempotency before retrying a billable request whose result you did not receive.

Next steps

Scrape options

Choose outputs, rendering, screenshots, and response handling.

API keys

Rotate or revoke keys and inspect usage by service.

Team access

Invite teammates and choose their organization roles.

Billing and usage

Manage shared credits and inspect individual charges.