usedino.dev valid
Dino
The deterministic verification layer for APIs. Dino gives coding agents and CI an independent, machine-readable verdict on an API: the same evidence and policy always produce the same result. You drive local scans through the published CLI (`@dino-hq/cli`), no account needed. Agents set up a Dino Organization and its APIs through the hosted MCP server at https://api.usedino.dev/mcp (a remote URL you connect over OAuth, not an npm package: there is no `@dino-hq/mcp-server` to install); the human
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://usedino.dev/llms.txt
- llms-full.txt
- https://usedino.dev/llms-full.txt
- Sections
- 6
- Links
- 18
- Size
- 7753 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T10:04:00.745Z
- Last checked
- 2026-10-27T10:04:01.529Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:04:00.749Z. Cached copy · Source on usedino.dev
# Dino
> The deterministic verification layer for APIs. Dino gives coding agents and CI an independent, machine-readable verdict on an API: the same evidence and policy always produce the same result. You drive local scans through the published CLI (`@dino-hq/cli`), no account needed. Agents set up a Dino Organization and its APIs through the hosted MCP server at https://api.usedino.dev/mcp (a remote URL you connect over OAuth, not an npm package: there is no `@dino-hq/mcp-server` to install); the human verifies their email, chooses or creates the Organization, confirms its residency, and approves access in the browser. Authorizing a Target Connection is decided only by the human, signed in to Dino on its approval page (the `approvalUrl` the agent hands over); Dino refuses that decision from an agent. Other human work (an OAuth2 connect journey, stopping access, Dino service keys) happens on Dino's task page: the agent starts or requests it (`start_connect_journey`, `request_operator_action`), hands the human the `taskUrl`, and reads the outcome; Dino service keys are issued only by a human, and `list_service_keys` never returns key material. Agents also run Discovery over MCP: `find_apis` and `get_api_estate` recover the exact estate from an API's name, `open_source_intake` brings an OpenAPI or SDL file's exact bytes to Dino without passing through the model, `get_discovery_generation` with `include: "inventory"` reads the canonical inventory in pages, `revoke_discovery_source` withdraws a wrong source, and `request_discovery_source_erasure` erases a stored source only after a human approves it.
This site is static content on usedino.dev. The canonical URL for this file is **https://usedino.dev/llms.txt** (the short paths `/llms` and `/llm.txt` redirect here). For the complete documentation in a single file, see llms-full.txt below.
## For coding agents: how to set up and run Dino
You (the agent) drive the `dino` CLI. A human supplies values you do not have (API URL, secrets) when Dino asks. The canonical, version-matched copy of this skill ships inside the CLI (run `dino skill`); this is a snapshot so you can start from a cold workspace. `dino schema` prints every command, flag and exit code of the installed version as JSON.
The loop: set up, verify, read, fix, reverify.
1. Install: `curl -fsSL https://usedino.dev/install.sh | sh` (standalone binary, no Node.js on macOS and most Linux; where no binary fits (e.g. Alpine/musl) it falls back to npm, which needs Node.js 22+; in scripts and agents run it under `bash -o pipefail -c '…'` and pin a version with `sh -s <version>`), or `brew install dino-hq/tap/dino`, or `npm install -g @dino-hq/cli` (Node 22+), or run pinned with no install: `npx -y @dino-hq/cli@<version>`. No account is needed for local scans.
2. Set up (once per project): `dino init --endpoint <API_URL> --protocol <graphql|rest> --auth <none|header|oauth2>` writes a flat `.dino.yml`. Add `--yes` for non-interactive / agent use.
…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 |
|---|---|---|---|---|---|---|---|
| dosu.dev | Dosu | interface AI agents and MCP Developer tools | US | 56 | ✓ | ✓ | |
| clirank.dev | CLIRank | interface Finance and payments Developer tools +2 | US | 45 | ✓ | ✓ | |
| oversecured.com | Oversecured Docs | interface Cybersecurity Developer tools | — | 52 | ✓ | ✓ | |
| codesamplex.dev | CodeSampleX | interface AI agents and MCP Developer tools | KR | 48 | ✓ | ||
| happier.dev | Happier | documentation AI agents and MCP Developer tools | — | 48 | ✓ | ||
| verified-skill.com | Verified Skill | documentation AI agents and MCP Developer tools | — | 47 | ✓ | ||
| agentmarkup.dev | agentmarkup | interface Developer tools APIs and SDKs | RO | 45 | ✓ | ✓ | |
| xano.com | Xano | interface AI agents and MCP Infrastructure +1 | US | 56 | ✓ |
Machine-readable: GET /v1/resolve?q=usedino.dev · GET /v1/domain/usedino.dev · 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 usedino.dev, 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 usedino.dev:
1. POST https://agentwebmap.com/v1/sites/usedino.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://usedino.dev/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/usedino.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/usedino.dev).
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.