dryburgh.com valid
Dryburgh
Research and strategy for the compute economy.
- Authority
- 45 reach 6 · trust 5 · quality 19 · freshness 15
- Tier
- listed
- llms.txt
- https://dryburgh.com/llms.txt
- Sections
- 8
- Links
- 9
- Size
- 1698 bytes
- Popularity rank
- #631608
- Registered
- 1999-02-09
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-19T10:44:24.832Z
- Last checked
- 2026-10-21T10:30:01.697Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-21T10:30:00.777Z. Cached copy · Source on dryburgh.com
# Dryburgh
> Research and strategy for the compute economy.
See where AI is heading. Get more from every dollar you spend on AI. Know when to spend on people and when on compute. Multiply what your teams can do.
Canonical site: https://dryburgh.com
Role: The Compute Economy
## Category
The Compute Economy
## What this firm is
A research and strategy firm on the compute economy.
## Analysis
- [What the CFO should measure before replacing headcount with compute](https://dryburgh.com/analysis/what-the-cfo-should-measure): Activity is not capacity. Accepted output is.
- [Verification is the binding constraint](https://dryburgh.com/analysis/verification-is-the-constraint): When cognition is cheap, the scarce step is establishing that an answer is true.
## Data
- [Compute economy indicators](https://dryburgh.com/data/compute-economy-indicators): data as of 2026-09-10, snapshot 2026-09-10.1
## Figures
- [Of three epoch.ai URLs tested, how many had moved](https://dryburgh.com/figures/epoch-url-drift): 2 of 3 — true as of 2026-09-11, quarter-stable
- [Rows in this house's own source-errata register](https://dryburgh.com/figures/errata-register-size): 684 rows — true as of 2026-09-11, week-stable
## Methods
- [How URL stability is tested](https://dryburgh.com/methods/how-we-test-url-stability): how a claim on this site was established
- [How the errata register is counted](https://dryburgh.com/methods/how-we-count-the-register): how a claim on this site was established
## Corrections
- [Corrections register](https://dryburgh.com/corrections): what this house got wrong, when, and how that was established
## Pages
- [Colophon](https://dryburgh.com/colophon)
Machine-readable: GET /v1/resolve?q=dryburgh.com · GET /v1/domain/dryburgh.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.
Own or manage this website?
If you own or manage dryburgh.com, 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 dryburgh.com:
1. POST https://agentwebmap.com/v1/sites/dryburgh.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://dryburgh.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/dryburgh.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/dryburgh.com).
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.