This page describes the machine-readable interfaces available for agents and integrations on in-answer.ai.
Agent discovery: the homepage advertises these resources via
RFC 8288
Link headers:
rel="api-catalog" and rel="service-doc".
The machine-readable API catalog is available at
/.well-known/api-catalog, served as
application/linkset+json per
RFC 9727 and
RFC 9264. Each entry carries
service-desc, service-doc and status links.
| Resource | URL |
|---|---|
| Blog API OpenAPI 3.1 description | /docs/api/openapi.json |
| MCP tool manifest | /docs/api/mcp.json |
| Blog API health | https://xadbqmpogsskiwmstywo.supabase.co/functions/v1/blog-api/health |
Agents can discover how to authenticate via /.well-known/openid-configuration (OIDC Discovery) and /.well-known/oauth-authorization-server (RFC 8414). Protected-resource metadata is at /.well-known/oauth-protected-resource.
| Property | Value |
|---|---|
| Issuer | https://xadbqmpogsskiwmstywo.supabase.co/auth/v1 |
| Authorization endpoint | /oauth/authorize |
| Token endpoint | /oauth/token |
| JWKS | /.well-known/jwks.json |
| Grant types | authorization_code, refresh_token (PKCE S256) |
| Dynamic client registration | /oauth/clients/register |
Agent entry points are also advertised through DNS under the
_agents namespace, using ServiceMode
SVCB records as described in
DNS for AI Discovery.
_index._agents.in-answer.ai. 3600 IN SVCB 1 in-answer.ai. alpn="h2,http/1.1" port=443 mandatory=alpn,port _mcp._agents.in-answer.ai. 3600 IN SVCB 1 in-answer.ai. alpn="h2,http/1.1" port=443 mandatory=alpn,port
The zone is signed with DNSSEC so validating resolvers return authenticated data.
in-answer exposes a Model Context Protocol (MCP) server for AI agents. Agents can use it to learn about in-answer, list published blog posts, and read individual articles.
| Property | Value |
|---|---|
| Endpoint | https://xadbqmpogsskiwmstywo.supabase.co/functions/v1/mcp |
| Protocol | MCP |
| Authentication | None required for public tools |
A REST API for creating, updating, and publishing blog posts programmatically. It is intended for internal team use and requires a valid API key.
| Property | Value |
|---|---|
| Endpoint | https://xadbqmpogsskiwmstywo.supabase.co/functions/v1/blog-api |
| Authentication | x-api-key header |
POST https://xadbqmpogsskiwmstywo.supabase.co/functions/v1/blog-api/posts
Content-Type: application/json
x-api-key: YOUR_API_KEY
{
"title": "My new post",
"content_html": "<h2>Hello world</h2><p>Body text here.</p>",
"status": "published",
"tags": ["ai-visibility"]
}
For access, API keys, or integration questions, contact the in-answer team via the homepage contact form.