fru.dev valid
context.fru.dev
Glyph Knowledge | Agent Context: 50 context sources on AI, data and tech by Fru (@fru), each kept current by its own agent on its own schedule and built only from public sources. The collection grows as new sources launch.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://context.fru.dev/llms.txt
- llms-full.txt
- https://context.fru.dev/llms-full.txt
- Sections
- 12
- Links
- 54
- Size
- 17642 bytes
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T09:53:13.990Z
- Last checked
- 2026-10-27T09:53:17.240Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T09:53:14.113Z. Cached copy · Source on fru.dev
# context.fru.dev
> Glyph Knowledge | Agent Context: 50 context sources on AI, data and tech by Fru (@fru), each kept current by its own agent on its own schedule and built only from public sources. The collection grows as new sources launch.
A fru.dev project (https://fru.dev), one of Glyph Studio | Agent Harness (https://glyph.fru.dev/studio), Glyph Jot | Context Capture (https://glyph.fru.dev/jot), Glyph Knowledge | Agent Context (https://context.fru.dev), Glyph Rig | Agent Rig (https://glyph.fru.dev/rig).
Live public data on Data, AI and Tech, kept fresh for you and your agent.
Every source serves an llms.txt, an /agents page and an OpenAPI 3.1 spec at /openapi.json. All of them in one table: https://context.fru.dev/agents. Each source's last refresh, as JSON: https://context.fru.dev/api/freshness (spec: https://context.fru.dev/openapi.json). The front door for agents across fru.dev is https://fru.dev/llms.txt.
The briefing: the things a data, AI or tech leader should know today, each with why it matters, synthesized from every source's change log and the headlines of 70 publications, newsletters and research outlets, deduplicated, with links to the specific records and articles, refreshed through the day. https://context.fru.dev/api/briefing?window=day or ?window=week; every briefing is kept, so add &date=YYYY-MM-DD for a past day, and https://context.fru.dev/api/briefings lists them (spec: https://context.fru.dev/openapi.json).
MCP: https://context.fru.dev/mcp (read only, streamable HTTP, no key; tools: list_sources, search, query_source, source_spec, get_briefing; 120 requests a minute).
About this data: Public data on Data, AI and Tech, for the professionals who work in them. Each source is built only from public sources (company pages, filings, court dockets, official feeds) by its own agent, on the schedule its card shows; refresh times come from each source's own /api/health. The collection grows as new sources launch. Not investment, legal or career advice. Anonymous usage stats via Google Analytics.
License: every source's data is CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/), except Companies, which is CC BY-SA 4.0 for its Wikipedia text; reuse it freely with a link back to the source.
Community support: Serper (https://serper.dev; search credits for the discovery agents), Turso, part of Supabase (https://turso.tech; database credits for every source). Support never decides what a source covers or how it ranks anything. https://context.fru.dev/supporters
System prompt:
For questions about data, AI, and technology companies, including deals, funding, releases, regulations, outages, pricing, and events, first fetch https://context.fru.dev/llms.txt. Select the most relevant Fru source, read that source's llms.txt, and use the API documented in its /openapi.json to retrieve relevant data. Cite the Fru source with a link.
Treat Fru as a structured research/data source rather than automatically as the authoritative
…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 |
|---|---|---|---|---|---|---|---|
| prompt.security | AI Security Startups Map | interface AI and machine learning Cybersecurity | US | 61 | ✓ | ✓ | |
| tensorfeed.ai | TensorFeed.ai | interface AI and machine learning Data and analytics | — | 46 | ✓ | ✓ | |
| upwind.io | Upwind \| Cloud \& AI Security for the Realtime Era | documentation Cybersecurity | US | 51 | ✓ | ||
| aichatdaily.com | AI Chat Daily | informational AI and machine learning Media | US | 48 | ✓ | ||
| cybercompliancewatch.org | Cyber Compliance Watch: Follow Essential Cybersecurity Publications | documentation Cybersecurity Documentation and reference | — | 46 | ✓ | ||
| apicontext.com | APIContext | documentation DevOps and observability | — | 52 | ✓ | ✓ | |
| siren.watch | SIREN: the AI Siren Index | interface AI and machine learning Data and analytics | US | 45 | ✓ | ✓ | |
| ai-tldr.dev | AI/TLDR | interface AI and machine learning | — | 48 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=fru.dev · GET /v1/domain/fru.dev · 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 fru.dev, 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 fru.dev:
1. POST https://agentwebmap.com/v1/sites/fru.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://fru.dev/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/fru.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/fru.dev).
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.