trustysquire.ai valid
Trusty Squire
Empower agents with auth and payments.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://trustysquire.ai/llms.txt
- llms-full.txt
- https://trustysquire.ai/llms-full.txt
- Sections
- 5
- Links
- 14
- Size
- 2514 bytes
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T18:56:30.908Z
- Last checked
- 2026-10-25T18:56:32.624Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T18:56:30.919Z. Cached copy · Source on trustysquire.ai
# Trusty Squire
> Empower agents with auth and payments.
Trusty Squire is an MCP server that gives Claude Code, Codex, Cursor, OpenCode, Goose, and other coding agents the ability to provision, ship, and pay on your behalf. It signs up for and configures real websites, wires up OAuth, Stripe, and deploys, and can complete purchases and coordinate on your behalf — your keys and card never leave the vault.
## Why it exists
Trusty Squire is not a secrets manager for keys you already have, and not a browser-automation framework you script per site. Operator-style browser tools often stall at signup walls and bot detection; Trusty Squire works through those, provisions the real account or completes the real purchase, and captures the resulting credential or payment without returning the raw secret or card to the agent, chat, source code, or the project's .env file.
## Install
`npx @trusty-squire/mcp connect`
Free to start.
## Safety boundary
- Provider credentials are captured into an encrypted, write-only vault.
- Credential tools use references and server-side injection instead of returning stored plaintext.
- Deployed backends can receive host-scoped, auditable, revocable egress grants. The grant token is returned once through MCP and can enter agent context; it is not the provider key. Use `use_credential` when zero grant-token exposure is required.
- A run stops for a phone requirement, hard CAPTCHA, or human decision instead of guessing.
## Key URLs
- [Website](https://trustysquire.ai/)
- [Supported services](https://trustysquire.ai/services)
- [Problem guides](https://trustysquire.ai/guides)
- [Product comparisons](https://trustysquire.ai/compare)
- [Coding-agent integrations](https://trustysquire.ai/integrations)
- [OpenCode integration](https://trustysquire.ai/integrations/opencode)
- [Install guide](https://trustysquire.ai/start)
- [GitHub repository](https://github.com/trusty-squire/trusty-squire)
- [npm package](https://www.npmjs.com/package/@trusty-squire/mcp)
## Reviewed service examples
- [Braintrust](https://trustysquire.ai/services/braintrust): reviewed signup and credential flow
- [Cerebras](https://trustysquire.ai/services/cerebras): reviewed signup and credential flow
- [Clerk](https://trustysquire.ai/services/clerk): reviewed signup and credential flow
- [DeepInfra](https://trustysquire.ai/services/deepinfra): reviewed signup and credential flow
- [Zilliz Cloud](https://trustysquire.ai/services/zilliz): reviewed signup and credential flow
Machine-readable: GET /v1/resolve?q=trustysquire.ai · GET /v1/domain/trustysquire.ai · 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 trustysquire.ai, 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 trustysquire.ai:
1. POST https://agentwebmap.com/v1/sites/trustysquire.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://trustysquire.ai/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/trustysquire.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/trustysquire.ai).
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.