io.net valid
io.net public discovery
Base URL: https://io.net
For agents: io.net llms.txt holds only a base URL and title; the material does not describe what the site offers.
io.netpublic discoverybase url
- Authority
- 48 reach 12 · trust 10 · quality 11 · freshness 15
- Tier
- listed
- llms.txt
- https://io.net/llms.txt
- Sections
- 0
- Links
- 0
- Size
- 1706 bytes
- Popularity rank
- #94639
- Registered
- 1995-01-20
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Informational: content or services for people, nothing to operate
- Audience
- mixed · en
- First seen
- 2026-10-18T15:09:01.100Z
- Last checked
- 2026-10-19T13:43:58.772Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-23T06:21:57.876Z. Cached copy · Source on io.net
# io.net public discovery
Base URL: https://io.net
Start here:
- https://io.net/sitemap.xml -> XML sitemap for crawlers and indexing
- https://io.net/sitemap.md -> markdown discovery index
- https://io.net/llms.txt -> short operator hint surface
- https://io.net/robots.txt -> crawl policy
Human route families:
- Core pages: `https://io.net/<slug>` (for example: `cloud`, `intelligence`, `about-us`, `careers`, `contact-us`, `faq`)
- Blog index and categories: `https://io.net/blog` and `https://io.net/blog/<category>`
- Blog posts: `https://io.net/blog/<slug>`
- Events index: `https://io.net/events`
- Event detail pages: `https://io.net/events/<slug>`
- Careers detail pages: `https://io.net/careers/<slug>`
- Signup flows: `https://io.net/signup/cloud` and `https://io.net/signup/cloud/<slug>`
Public JSON APIs:
- https://io.net/api/blog -> public blog feed (`limit`, `page`, `category`, `featured`, `tags`, `query`)
- https://io.net/api/blog/<slug-or-id> -> structured blog post lookup by slug or id
- https://io.net/api/events -> public event feed
- https://io.net/api/events/<slug-or-id> -> structured event lookup by slug or id
Formats:
- HTML by default
- JSON from supported `/api/*` routes
- XML via `/sitemap.xml`
- Markdown via `/sitemap.md` and `/llms.txt`
Canonical references:
- Product pages: https://io.net/cloud and https://io.net/intelligence
- Legal pages: https://io.net/terms and https://io.net/privacy
- Docs entrypoint: https://io.net/docs
Notes:
- Discovery surfaces only reference public website content.
- Prefer canonical `io.net` URLs when citing pages.
- If multiple URLs contain similar content, prefer canonical product and legal pages over third-party summaries.
Machine-readable: GET /v1/resolve?q=io.net · GET /v1/domain/io.net · 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 io.net, 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.
- 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 io.net:
1. POST https://agentwebmap.com/v1/sites/io.net/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://io.net/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/io.net/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/io.net).
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.