generated: '2026-08-13' method: probed source: probe of every Teads / Outbrain host named in apis.yml description: >- Probe of the standard .well-known discovery surface plus /llms.txt across every host this provider names — the developer portal, the Conversions API host, the In-Chat Recommendations API host, and the corporate site. ONE real document was found: an RFC 9116 security.txt served for mv.outbrain.com (the documented In-Chat API host), which 302s to the same document on www.outbrain.com. Outbrain and Teads are the same company — Outbrain Inc. acquired Teads in 2025 and the combined business operates under the Teads brand — so that host is this provider's own. Everything else 404s, or is refused with 406 by the WAF in front of www.teads.com / www.outbrain.com for any non-HTML request. No agent card, no OpenID/OAuth discovery, no api-catalog, no ai-plugin. hosts: - host: mv.outbrain.com role: Teads In-Chat Recommendations API baseURL documents: - path: /.well-known/security.txt status: 200 file: teads-security.txt redirects_to: https://www.outbrain.com/.well-known/security.txt document: true note: RFC 9116 security.txt with Contact + Policy. No Expires field. - path: /.well-known/agent-card.json status: 404 - path: /.well-known/agent.json status: 404 - path: /.well-known/openid-configuration status: 404 - path: /.well-known/oauth-authorization-server status: 404 - path: /.well-known/api-catalog status: 404 - path: /.well-known/ai-plugin.json status: 404 - path: /llms.txt status: 404 - path: /openapi.json status: 404 - host: www.outbrain.com role: parent-brand corporate host serving the security.txt above documents: - path: /.well-known/security.txt status: 200 file: teads-security.txt document: true - path: /.well-known/agent-card.json status: 406 note: WAF refuses non-HTML requests. - path: /.well-known/agent.json status: 406 - path: /.well-known/api-catalog status: 406 - path: /llms.txt status: 406 - host: developers.teads.com role: developer portal (Docusaurus) documents: - path: /.well-known/security.txt status: 404 - path: /.well-known/agent-card.json status: 404 - path: /.well-known/agent.json status: 404 - path: /.well-known/openid-configuration status: 404 - path: /.well-known/oauth-authorization-server status: 404 - path: /.well-known/api-catalog status: 404 - path: /.well-known/ai-plugin.json status: 404 - path: /llms.txt status: 404 - path: /openapi.json status: 404 note: Returns the Docusaurus 404 HTML shell, not a spec. - path: /sitemap.xml status: 200 note: 93 documentation URLs; used for the docs sweep behind this enrichment pass. - host: ca.teads.tv role: Teads Conversions API baseURL documents: - path: /.well-known/security.txt status: 404 - path: /.well-known/agent-card.json status: 404 - path: /.well-known/agent.json status: 404 - path: /.well-known/openid-configuration status: 404 - path: /.well-known/oauth-authorization-server status: 404 - path: /.well-known/api-catalog status: 404 - path: /.well-known/ai-plugin.json status: 404 - path: /llms.txt status: 404 - path: /openapi.json status: 404 - path: /health status: 200 document: false note: Undocumented liveness endpoint; returns the plain string "server is up". - host: www.teads.com role: corporate site documents: - path: /.well-known/security.txt status: 406 note: >- The edge returns 406 for every non-HTML path on this host (also /llms.txt, /ads.txt, /sellers.json), including with a browser User-Agent and Accept header. HTML paths return 200 normally, so this is content-type refusal, not a bot block on the host. - path: /.well-known/agent-card.json status: 406 - path: /.well-known/agent.json status: 406 - path: /.well-known/api-catalog status: 406 - path: /llms.txt status: 406 summary: documents_found: 1 security_txt: true agent_card: false openid_configuration: false oauth_authorization_server: false api_catalog: false ai_plugin: false llms_txt: false checked: '2026-08-13'