We proudly respect robots.txt
NeuroAPI checks every target URL against the site's robots.txt before fetching. Disallowed paths are refused at the API layer for scrape, crawl, map, batch, search, extract, summary, screenshot, highlights, branding, interact, and question endpoints — including requests issued via our MCP server. Publisher crawl preferences are a first-class constraint of the platform, not an afterthought.
You must not
- Use the Service to violate any law or third-party right
- Attempt to bypass our
robots.txtenforcement, or access content in violation of a site's terms or applicable computer-fraud laws - Collect personal data, credentials, payment details, or protected health information from any site without a lawful basis
- Circumvent paywalls, login walls, anti-bot measures, or rate limits in a manner that exceeds reasonable, lawful research
- Generate spam, phishing content, malware, or material that infringes intellectual property
- Build datasets for surveillance, stalking, harassment, doxxing, or unlawful discrimination
- Resell raw API access, MCP credentials, or credits without a written agreement
- Test or attack our infrastructure outside our coordinated disclosure program
- Use the Service to train foundation models in violation of source-site terms
Rate & volume limits
Free and paid plans include concurrency limits documented in the rate-limits docs. Sustained abuse, suspicious traffic patterns, or extreme target-site impact may result in throttling or suspension.
Reporting abuse
If you believe an account is misusing the Service against your site or against you, email abuse@neuroapi.me. Include URLs, timestamps, and request identifiers if available. We respond within 2 business days.
Enforcement
We may, with or without notice, throttle, suspend, or terminate accounts that violate this policy. Serious violations are reported to law enforcement.