usenash.com valid
Nash
## Agent Instructions
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T20:55:37.390Z. Cached copy · Source on usenash.com
# Nash
> ## Agent Instructions
> Nash exposes two MCP servers. The docs MCP server at https://docs.usenash.com/mcp searches this documentation and needs no credentials. The Nash MCP server at https://mcp.usenash.com/mcp operates an organization's deliveries and needs a Nash API key. See https://docs.usenash.com/reference/build-with-ai.
> Use the Sandbox environment (https://api.sandbox.usenash.com/v1) for anything that creates or dispatches deliveries during development.
- [How Nash works](https://docs.usenash.com/reference/how-nash-works.md): A complete overview of the Nash delivery orchestration platform — the delivery lifecycle, the provider network, and the core building blocks you integrate with.
- [Plan your integration](https://docs.usenash.com/reference/plan-your-integration.md): How to plan a Nash API integration: timeline, account setup, dispatch strategies, notifications, and go-live.
- [API key and Org ID](https://docs.usenash.com/reference/generating-api-key-and-org-id.md): Create an API key in the Nash Portal and find the Organization ID to send with your requests.
- [Authentication](https://docs.usenash.com/reference/authentication.md): Authenticate Nash API requests with a Bearer API key and the Nash-Org-Id header.
- [Single sign-on](https://docs.usenash.com/reference/single-sign-on.md): Nash Portal sign-in can be connected to your own identity provider over OpenID Connect or SAML 2.0.
- [Roles and access](https://docs.usenash.com/reference/roles-and-access.md): How Nash roles and feature permissions work, recommended user groups to start from, and how to keep configuration and credentials restricted.
- [Environments](https://docs.usenash.com/reference/environments.md): Base URLs and Portal links for the Nash Production and Sandbox environments, and how Sandbox differs from Production.
- [Production testing](https://docs.usenash.com/guides/production-testing.md): How to schedule an integration testing call with Nash and get production API keys enabled.
- [Orders, jobs & dispatch](https://docs.usenash.com/reference/nash-api-overview.md): The key concepts behind the Nash API: orders, jobs, quoting, and dispatch.
- [Dispatch strategies](https://docs.usenash.com/reference/dispatch-strategies.md): How dispatch strategies control which providers can fulfill a job, how Nash selects one, what it can cost, when it dispatches, and how it recovers.
- [Delivery status](https://docs.usenash.com/reference/delivery-status.md): The normalized delivery statuses Nash reports across all providers, including terminal statuses and the guaranteed status order.
- [Delivery fees and pricing](https://docs.usenash.com/reference/delivery-fees-and-pricing.md): What a quote's price includes, which fees land on a delivery, how totalPriceCents is computed, and when each fee is final.
- [Delivery windows](https://docs.usenash.com/reference/delivery-windows.md): A delivery window is a bookable time slot, tied to a store location and bounded by capacity, that an
…
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 |
|---|---|---|---|---|---|---|---|
| nash.ai | Nash | documentation AI and machine learning AI agents and MCP | — | 52 | ✓ | ||
| neoagent.io | Neo Agent | interface AI and machine learning Productivity +2 | US | 46 | ✓ | ||
| routal.com | Routal | interface Logistics and shipping APIs and SDKs | US | 46 | ✓ | ||
| deliverect.com | Deliverect | interface Finance and payments Business software +1 | — | 54 | ✓ | ||
| vendodata.com | Vendo | informational | US | 45 | ✓ | ✓ | |
| nownodes.io | NOWNodes — AI & Developer Routing Index | interface AI and machine learning Infrastructure +2 | — | 61 | ✓ | ✓ | |
| orderly.network | Orderly Network | documentation Crypto and Web3 Developer tools | US | 60 | ✓ | ✓ | |
| wearepatchworks.com | Product documentation | interface Developer tools APIs and SDKs +1 | — | 46 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=usenash.com · GET /v1/domain/usenash.com · 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 usenash.com, 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 usenash.com:
1. POST https://agentwebmap.com/v1/sites/usenash.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://usenash.com/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/usenash.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/usenash.com).
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.