solo.one valid
SOLO Network API
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T11:53:17.125Z. Cached copy · Source on solo.one
# SOLO Network API
- [Overview](https://docs.solo.one/home/welcome.md): What the SOLO Network is, who participates in it, and where each kind of participant should start
- [How SOLO is different](https://docs.solo.one/home/why-solo.md): Why SOLO is a reusable trust network, not a data aggregator — and how the architecture makes verified work reusable
- [High-level concepts](https://docs.solo.one/home/overview.md): The six building blocks of the SOLO Network, the data flow that connects them, and how together they enforce privacy
- [Authentication](https://docs.solo.one/home/authentication.md): Authenticate with the SOLO Network API using WorkOS-issued bearer JWTs verified over JWKS
- [Errors](https://docs.solo.one/home/errors.md): The error response envelope, every HTTP status the API returns, and how to handle each one
- [Quickstart](https://docs.solo.one/home/quickstart.md): Get up and running on the SOLO Network in a few minutes
- [Furnishing your first entity](https://docs.solo.one/home/quickstart/furnish-an-entity.md): Contribute verified data about a consumer into a network
- [Querying your first product](https://docs.solo.one/home/quickstart/query-a-product.md): Record consent and read consolidated data back from the network
- [Joining a network](https://docs.solo.one/home/quickstart/join-a-network.md): Understand membership, roles, and your first calls in a network
- [Golden path: business lending onboarding](https://docs.solo.one/home/quickstart/business-lending-onboarding.md): Onboard a business by reusing verified trust assets first, then contributing only the work you had to do yourself
- [Golden path: consuming network data](https://docs.solo.one/home/quickstart/network-consumption.md): The reuse-first decision pattern — check what verified work exists, reuse it, and do only what is missing
- [Products](https://docs.solo.one/products/overview.md): The standardized data sets you query and furnish on the SOLO network
- [KYC Certificate](https://docs.solo.one/products/kyc-certificate-snapshot.md): Reusable consumer identity-verification certificate for onboarding
- [KYB Certificate](https://docs.solo.one/products/kyb-certificate-snapshot.md): Reusable business-verification certificate for business onboarding
- [Bank-Specific Bad Actor List](https://docs.solo.one/products/bank-specific-bad-actor-list.md): Sponsor-bank-scoped screening for repeat policy violators
- [Cross-Bank Financial Crimes Watch List](https://docs.solo.one/products/cross-bank-financial-crimes-watch-list.md): 314(b) consortium screening for inter-bank financial-crimes signals
- [Confirmed Fraud Attribute List](https://docs.solo.one/products/confirmed-fraud-attribute-list.md): Consortium screening for identifying attributes tied to confirmed fraud
- [Coverage Check](https://docs.solo.one/products/coverage-check.md): Non-billable pre-flight of field coverage before running a query
- [Trust assets](https://docs.solo.one/concepts/trust/trust-assets.md): The reusable unit
…
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 |
|---|---|---|---|---|---|---|---|
| voveid.com | VOVE ID | interface Authentication and identity APIs and SDKs | MA | 46 | ✓ | ✓ | |
| waldo.ai | Waldo AI Docs | documentation Cybersecurity | — | 46 | ✓ | ✓ | |
| skyfire.xyz | Skyfire Developer Portal Documentation | interface Developer tools AI and machine learning +3 | — | 52 | ✓ | ||
| kycaid.com | KYCAID | interface Finance and payments Cybersecurity +1 | — | 55 | ✓ | ||
| signzy.com | Signzy – Global Identity Verification and Compliance Platform | interface Finance and payments Authentication and identity +1 | US | 55 | ✓ | ||
| yapily.com | Yapily API Documentation | interface Finance and payments APIs and SDKs | — | 56 | ✓ | ✓ | |
| developer-docs.amazon | Selling Partner API Documentation | interface APIs and SDKs | — | 51 | ✓ | ||
| squads.so | Squads Docs | documentation Crypto and Web3 Developer tools | — | 49 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=solo.one · GET /v1/domain/solo.one · 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 solo.one, 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 solo.one:
1. POST https://agentwebmap.com/v1/sites/solo.one/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://solo.one/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/solo.one/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/solo.one).
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.