hol.org valid

Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.

Manage this listing — optional · Visit publisher ↗

Claim my listing on Agent Web Map for hol.org:
1. POST https://agentwebmap.com/v1/sites/hol.org/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://hol.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/hol.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/hol.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory. Ownership management is optional.

HOL (Hashgraph Online): Open Standards and Infrastructure for AI Agents

HOL, also known as Hashgraph Online, builds open standards, registries, developer infrastructure, and runtime security for AI agents. The portal hosts HOL Guard, the Universal Agentic Registry, HOL Points, HCS standards, and public developer resources.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T09:55:36.053Z. Cached copy · Source on hol.org

# HOL (Hashgraph Online): Open Standards and Infrastructure for AI Agents

> HOL, also known as Hashgraph Online, builds open standards, registries, developer infrastructure, and runtime security for AI agents. The portal hosts HOL Guard, the Universal Agentic Registry, HOL Points, HCS standards, and public developer resources.

This file is an optional, community-proposed llms.txt index for AI assistants and crawlers. It does not replace product documentation, OpenAPI contracts, OAuth metadata, or the terms that apply to a service.

## When to use HOL

Use HOL when a user or software agent needs to:

- discover AI agents, MCP servers, plugins, skills, protocols, or service endpoints across multiple registries;
- resolve a Universal Agent ID or inspect an agent profile, capability, protocol, availability signal, provenance record, or trust signal;
- search for a machine-callable agent that can perform a specific job;
- understand the layers of AI agent infrastructure and the steps required to make an agent discoverable;
- implement interoperable agent identity, profiles, communication, registries, payments, privacy, state, or audit workflows with open HCS standards;
- find HOL SDKs, specifications, examples, APIs, tutorials, or open-source repositories;
- test a typed HOL request without credentials or side effects;
- protect AI agents and automation by controlling supported commands, tool calls, installs, and configuration changes;
- understand HOL as an organization, contact its maintainers, or verify its privacy and trust information.

Do not use a marketing page as an API schema. For programmatic calls, start with the root OpenAPI document and then follow the product-specific contract. Do not assume crawler permission grants access to private workspaces or protected APIs.

## Machine-readable entry points

- [Documentation index](https://hol.org/docs): Canonical map of HOL product documentation and machine interfaces
- [Markdown homepage](https://hol.org/): Send `Accept: text/markdown`; the response varies on `Accept` and `Accept-Encoding`
- [Root OpenAPI](https://hol.org/openapi.json): Stable discovery contract with unique operation IDs, typed parameters, response schemas, and authentication requirements
- [HOL Guard pricing Markdown](https://hol.org/pricing.md): Live plan prices, trials, limits, storage, and capabilities derived from the current pricing contract
- [Agent onboarding sandbox](https://hol.org/api/agent-sandbox): No-credential, no-billing, no-mutation JSON sandbox for ping and Registry-search validation
- [Registry OpenAPI](https://hol.org/registry/api/v1/openapi.json): Complete Universal Agentic Registry API contract
- [OAuth authorization-server metadata](https://hol.org/.well-known/oauth-authorization-server): RFC 8414 discovery
- [OAuth protected-resource metadata](https://hol.org/.well-known/oauth-protected-resource): RFC 9728 discovery for protected resources
- [Public MCP endpoint](https://hol.org/.well-known/mcp): Strea
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Help agents understand your site

Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.

Manage this listing → · Agent and API instructions

Machine-readable: GET /v1/resolve?q=hol.org · GET /v1/domain/hol.org · this page as Accept: application/json or text/markdown · MCP lookup_domain