agenticweb.wiki

wellfound.com agentic web readiness

D Manifest validity: 0% (0/1 valid, 1 security.txt error, 5 warnings) · Surface score 10 (coverage 10 + breadth 0 + conformance 0). 2 standards observed across 1 of 9 steps; 1 manifest present, 1 security.txt error, 5 warnings. Checked 2026-10-25 03:20:04 UTC. This grades the agent-facing files published at wellfound.com, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/wellfound.com.svg) · JSON · Markdown · Re-check now

Coverage by step

01 Discovernothing observed02 Identifynothing observed03 PermitOAuth Protected Resource and Authorization Server Metadata (as used for agent authorization), CIMD04 Readnothing observed05 Actnothing observed06 Coordinatenothing observed07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json		absent HTTP 404
AI Catalog well-known file
/.well-known/ai-catalog.json		absent HTTP 404
MCP Server Cards (SEP-2127)
/mcp/server-card		absent HTTP 404
Agent2Agent Protocol
/.well-known/agent-card.json		absent HTTP 404
llms.txt
/llms.txt		absent HTTP 404
AGENTS.md
/AGENTS.md		absent HTTP 404
Agent Skills
/.well-known/agent-skills/index.json		absent HTTP 404
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
/.well-known/api-catalog		absent HTTP 404
AI Crawler User-Agent Tokens in robots.txt
/robots.txt		no AI tokens
  • no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (partial)
  • no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
  • no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
security.txt (RFC 9116)
/.well-known/security.txt		errors
  • Expires: missing (RFC 9116 requires it)
  • Canonical: missing
View valid /.well-known/security.txt template for wellfound.com
Contact: mailto:security@wellfound.com
Expires: 2027-09-20T23:40:43Z
Canonical: https://wellfound.com/.well-known/security.txt
Preferred-Languages: en
Policy: https://wellfound.com/security-policy
auth.md
/auth.md		blocked HTTP 403
Open Knowledge Format
/okf/index.md		absent HTTP 404

What an agent can call

Standards observed

Cheapest next steps

  1. llms.txt: one Markdown index file; the most widely read agent-facing file
    Generate starter /llms.txt for wellfound.com
    # Wellfound

> Wellfound and what it offers to agents

Short notes an agent should know before using the site: what it is for, who runs it, how to cite it.

## Docs
- [Getting started](https://wellfound.com/docs/getting-started): the first page to read
- [API reference](https://wellfound.com/openapi.json): OpenAPI description

## Optional
- [Changelog](https://wellfound.com/changelog): what changed, newest first
  2. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "wellfound.com"}))
  3. AGENTS.md: instructions for coding agents working on or with the site
    Generate starter /AGENTS.md for wellfound.com
    # Wellfound for agents

Wellfound and what it offers to agents

## Read the data, not the HTML
- Index: https://wellfound.com/llms.txt
- API description: https://wellfound.com/openapi.json
- Discovery catalog: https://wellfound.com/.well-known/ard.json

## Calling
- MCP server (Streamable HTTP): https://wellfound.com/mcp
- Rate limits and authentication: describe them here

## Conventions
- How to cite or attribute content
- What not to do (no scraping of /account/, no automated sign-ups, etc.)

Contact: security@wellfound.com

Agent pre-flight & practical readiness

Preferred mode: exa_or_http_fetch. No structured agent endpoint was found. The page has readable text, so fetch it directly or through a search index.

Fetch: GET https://wellfound.com/ No structured agent endpoint was found. Fetch the public page or use a search index.

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 85954, JSON-LD Organization, WebSite, WebPage, BreadcrumbList, ListItem, FAQPage, Question, Answer.

AI crawler posture: open_to_all · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.

Readiness subscores: reach 19/20, readability 22/30, capabilities 2/35, conformance 0/15, total 43/100, grade C.

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules