FAQ
What happens if I don't set up forwarding?
AI crawlers continue to hit your canonical pages as before. You lose:
- Per-article policy enforcement (you can't block / paywall them on the
way in) - Per-agent traffic analytics
- The agent-payment revenue path
Your MCP endpoint at oasy.<your-domain>/mcp still works for clients
that explicitly opt in (Claude Desktop, ChatGPT connectors, Cursor) —
that's a different traffic path entirely.
What happens if I don't verify my domain?
Your MCP works at the long form: https://api.oasy.ai/api/mcp/<orgId>.
You can still hand that URL to Claude / ChatGPT / Cursor. You just don't
get the clean oasy.<your-domain>/mcp vanity URL, and the AI-traffic
landing pages don't have a host to live on.
Can I block a specific agent?
Not yet at the agent level. You can block specific articles via the
Block policy. Per-agent blocklists are on the roadmap — they're a
small change once we expose them.
How often do you re-crawl my site?
After the initial ingest, articles aren't auto-refreshed yet. We're
adding a daily sitemap diff that pulls new + updated articles. Today,
re-ingest is manual via support.
What if I take down an article?
It stays in our index until you delete it via support or the next
re-ingest. The body that gets served is the version we crawled. Article
takedowns + corrections are the most common roadmap ask — coming soon.
Can I see who's reading what?
Yes — every MCP call is in the Recent Calls table on /mcp, with
the agent UA, tool, status, and latency. With OAuth on, each row also
carries the install's client_id and (if captured) email.
How do you handle robots.txt?
We don't — the forwarding rule lives on your CDN and runs before
robots.txt is consulted. If you want to keep your robots.txt as-is for
agents that respect it, that's fine: those agents will skip your site
entirely. The forwarding rule only catches the ones who don't.
Is there an SLA?
Today: best-effort. We've been running Press Gazette in production since
May 2026 with no significant outages. A formal SLA comes with enterprise
contracts.
Can I use Oasy with a non-news publication?
Absolutely. Reviews sites, documentation hubs, data portals, recipe
sites — anything with discrete pages an agent might want to read.
The four built-in tools (search_articles, get_article, etc.) are
generic; the "article" framing is just naming.
Refund policy on agent payments?
Agent payments are non-refundable once the article body is served — same
posture as any paid API call. If an article serves but is malformed /
404s upstream, ping support and we'll credit it.