onevalor.com valid

LLMs.txt for onevalor.com

This file provides Large Language Models (LLMs) with accurate, up-to-date information about Valor for enhanced AI assistance and responses.

For agents: Valor resource hub for mineral owners and journalists: owner guides on leases, royalties and sales, plus Valor-computed statistics, press kit and case studies.

mineral rightsmineral ownersroyalty checksoil and gas leasesvalor statistics

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T22:26:03.582Z. Cached copy · Source on onevalor.com

# LLMs.txt for onevalor.com

> This file provides Large Language Models (LLMs) with accurate, up-to-date information about Valor for enhanced AI assistance and responses.

## Featured Recovery Case Study

Valor helped a royalty owner recover approximately $1.4 million in suspended revenue within the client's first six months. A review uncovered a title issue affecting six wells with one operator. Valor coordinated the resolution, and the funds were released by the end of August 2026. The full portfolio comprised 133 wells across 19 counties, two basins, and four states. This case study reflects one client’s experience. Past results do not guarantee future outcomes. Valor does not guarantee any recovery, recovery amount, or timeframe. Results depend on each portfolio’s circumstances and factors outside Valor’s control. Some engagements may result in no recovery.

- [Case study and summary](https://www.onevalor.com/mineral-management/#recovered-revenue-case-study)
- [Download the full case study — searchable PDF, 4 pages](https://cdn.onevalor.com/assets/case-studies/valor-1-4-million-suspended-revenue-six-months-v1.pdf)
- [Royalties in suspense — guide and video: why operators hold revenue, state deadlines and interest, and how Valor recovers it](https://www.onevalor.com/mineral-management/owners/royalties-in-suspense/)

## AI Agent Access

This site supports the **Model Context Protocol (MCP)** and a structured JSON API, both designed for AI agents. **No authentication, no session tokens, no visitor-token handshake, no scraping required.**

### MCP Endpoint (live tools)

- **MCP Endpoint:** https://www.onevalor.com/mcp (Streamable HTTP, stateless — POST JSON-RPC 2.0)
- **Human/AI-readable capabilities page:** open https://www.onevalor.com/mcp in a browser (GET with `Accept: text/html`) for a documented page with connection steps, HowTo schema, and a card per tool. Programmatic GET returns 405 by design.
- Custom mineral-industry tools, not generic site search:

| Tool | What it does |
|---|---|
| `about_valor` | Company overview, credentials, contact — and what Valor does NOT do (never buys minerals) |
| `search_glossary` | Search 123 mineral & royalty term definitions (division order, NRI, suspense, COPAS...) with deep links |
| `get_services_and_coverage` | Service catalog (owners, fiduciaries, operators) + states/basins served |
| `search_faq` | Canonical Q&A incl. payment deadlines, Regulation 9, UBIT |
| `get_resource_guides` | Guide catalog by audience — route users to the right in-depth page |
| `get_owner_situations` | Citable owner-situation answers (inherited minerals, lease offer, unclaimed funds, royalty checks) + guide URLs |
| `lookup_operator` | Look up Texas oil & gas operators by name in an 18,000+ organization directory (P-5 status + directory page) |
| `get_provider_due_diligence` | Checklists for evaluating a mineral manager or operator back-office provider — owner relations, accounting/JIB transition, records migration, outsou
…

Related sites

Find similar publishers by meaning →

Other listed sites in Energy and utilities. See the whole category →

Machine-readable: GET /v1/resolve?q=onevalor.com · GET /v1/domain/onevalor.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.

Claim my listing on Agent Web Map for onevalor.com:
1. POST https://agentwebmap.com/v1/sites/onevalor.com/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://onevalor.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/onevalor.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/onevalor.com).
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.