Coffee Blog
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
Discover content discover_content
List published posts and pages with titles, URLs, excerpts, and SEO metadata; pass an optional search_query to filter by topic.
contentdiscoverywordpressGet content by ID or URL get_content
Retrieve the full structured content, metadata, and SEO fields for a specific post or page by its WordPress ID.
contentAnalyze SEO of a post analyze_seo
Return the SEO score breakdown — keyword usage, meta tags, readability, and structured-data coverage — for a given post.
seoanalysisSEO recommendations get_seo_recommendations
Return prioritised, actionable SEO improvements for a specific post, including missing tags, keyword gaps, and schema suggestions.
seorecommendationsAuto-discover brand metadata auto_discover_brand
Return brand and site metadata: name, description, logo, sitemap URL, and llms.txt URL.
branddiscovery2026-10-22 from https://blog.coffee.ai/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.