Repository navigation
feat: 12.6 — agent-readable output (JSON-LD + agent.json/agent-card.json/llms.txt) - #8
Merged
Merged
Conversation
… agent-card.json, /llms.txt
Server-side JSON-LD in <head> plus proxied /.well-known/agent.json,
agent-card.json, and /llms.txt — all backed by api.tetapi.dev's
/wk/{entity_id}/* endpoints (docs/universal-tag.md Part B). More
reliable than the tag.js approach (12.5a) for agents that don't execute
JavaScript, since WordPress controls its own domain and can serve
/.well-known/* directly — no verify.tetapi.dev redirect needed (12.5c).
Same 15-min transient caching pattern as the existing badge. Nothing is
served for a site with no entity connected yet (real 404s, no
default/placeholder data). Reuses the redirect_canonical fix from 1.0.1
for these new routes too.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
<head>(wp_head), proxyingGET /wk/{entity_id}/agent.json— reliable for agents that don't execute JS, unlike the tag.js approach (12.5a)/.well-known/agent.json,/.well-known/agent-card.json,/llms.txt— WordPress rewrite rules proxying the matchingapi.tetapi.dev/wk/{entity_id}/*endpointTetapi_Api::get_wk_file()is the raw-proxy counterpart toget_public_profile())redirect_canonicalfix for these three new routes (same WP trailing-slash issue applies)Test plan
hellfire-solutionsentity (id0fab67ea-0283-42b1-87a1-4b779817d624)<head>byte-matches the live/wk/.../agent.jsonresponse/.well-known/agent.json→ 200 with correct data/.well-known/agent-card.json→ 200 with correct data/llms.txtproxy logic confirmed correct content-type + body via direct function call (browser address-bar nav to a bare root path was flaky in the test harness, not a plugin issue — same code path as the two files that navigated cleanly)/.well-known/agent.jsonreturns a real 404Not doing (per task): the
tag.js/sendBeaconmechanism (12.5a) — irrelevant, WordPress isn't a non-CMS site.Co-Authored-By: Claude Fable 5 noreply@anthropic.com