vlm.run valid
VLM Run
The unified gateway for document, image, and video AI. Open-weight vision models behind one OpenAI-compatible API — Orion, our visual agent, sees, reasons, and acts when you need more than raw models.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T11:19:01.374Z. Cached copy · Source on vlm.run
# VLM Run
> The unified gateway for document, image, and video AI. Open-weight vision models behind one OpenAI-compatible API — Orion, our visual agent, sees, reasons, and acts when you need more than raw models.
Key terms: Visual Intelligence, Vision-Language Model, VLM, Orion, Visual Agent, Document OCR, Structured Output, Visual Grounding, HIPAA, SOC 2, Computer Vision, Multimodal AI, Visual ETL, API
Get started in [Studio](https://app.vlm.run). Agents can create an account, or authorize an existing account, over HTTP. Read the [authentication runbook](https://vlm.run/auth.md), [CLI skill](https://vlm.run/SKILL.md), and [Gateway skill](https://vlm.run/gateway/SKILL.md).
## Setup for an assistant
1. Check a saved VLMRUN_API_KEY with GET https://api.vlm.run/v1/models and a bearer header. Never print the key. A 200 means setup is done. On 403, recover a key from Studio or continue signup for that email. Do not use /v1/openai/models as a credential check; it returns 200 with no key.
2. With no working key, get the human's email. POST https://prod-vlm-cloud-nfsnfpr33q-uc.a.run.app/api/v1/agent/accounts with Content-Type: application/json and {"email":"ada@example.com"}. Save the returned signup_token privately; the code expires in 10 minutes. account_status is "new" or "existing". No account is created yet.
3. If a mail tool is connected to that inbox, read vlm-verification-code from the message sent after this request. The subject is "Verify your email for VLM Run", or "Authorize AI assistant for your VLM Run account" when account_status is "existing". Do not print the code. Otherwise ask the human. Ask for first/last name when unknown, and for an explicit agreement to https://vlm.run/terms-of-service and acknowledgement of https://vlm.run/privacy before verify. Agreeing authorizes account creation or a new API key for this assistant.
4. POST https://prod-vlm-cloud-nfsnfpr33q-uc.a.run.app/api/v1/agent/accounts/verify with {"signup_token":"<saved token>","code":"849201","first_name":"Ada","last_name":"Lovelace","terms_accepted":true}. Omit names when not provided. Keep the code a string.
5. On 200, save api_key as VLMRUN_API_KEY in the approved secret store; the response also includes api_key_id, organization_id, credits_granted_dollars, account_status, and studio_url. Never paste the key or full response into chat. New accounts get $0.50 trial credit; existing accounts get a new key and 0 credits. Tell the human: no password was set; sign into Studio via "Email me a sign-in code". New accounts unlock the rest of the welcome credit after that sign-in.
6. Confirm the key with GET https://api.vlm.run/v1/models, then follow https://vlm.run/SKILL.md for Orion on images, video, and documents, or https://vlm.run/gateway/SKILL.md for parse, chat, embeddings, and transcription.
Show validation errors in the terminal. Errors use {"detail":{"code":"...","message":"..."}}. For 400 invalid_input, display detail.message and detail.field and ask for correc
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| wiro.ai | Wiro AI | interface AI and machine learning APIs and SDKs +1 | US | 50 | ✓ | ||
| ofox.ai | OfoxAI | interface AI and machine learning APIs and SDKs +1 | — | 55 | ✓ | ✓ | |
| orq.ai | Orq.ai | interface AI and machine learning AI agents and MCP +1 | CA | 59 | ✓ | ✓ | |
| edenai.co | Eden AI | interface AI and machine learning APIs and SDKs | FR | 52 | ✓ | ||
| aireserve.com | AI Reserve — llms.txt (index pointer) | interface AI and machine learning APIs and SDKs | US | 48 | ✓ | ✓ | |
| eachlabs.ai | eachlabs | interface AI and machine learning APIs and SDKs | US | 58 | ✓ | ✓ | |
| tryleap.ai | Leap | interface AI and machine learning APIs and SDKs | US | 58 | ✓ | ||
| router.com | Ramp Router | interface AI and machine learning AI agents and MCP +1 | — | 54 | ✓ |
Machine-readable: GET /v1/resolve?q=vlm.run · GET /v1/domain/vlm.run · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage vlm.run, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for vlm.run:
1. POST https://agentwebmap.com/v1/sites/vlm.run/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://vlm.run/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/vlm.run/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/vlm.run).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.