API Terms

Access, rate limits, security, and data use rules for our APIs and agent integrations.

Version
1.0
Status
Draft — pending legal review
Effective
2026-01-01
Reading time
2 min

Access and credentials

API and agent credentials are issued to a named account, must be kept secret, and may not be shared or embedded in client-side code.

Acceptable use

  • Respect published rate limits and back off on error responses
  • Do not use the API to harvest content in bulk or to build a competing dataset or model
  • Do not attempt to access data outside your authorized scope

Data handling

Data retrieved through the API may be used only to deliver the integration's stated function, must be secured to at least the standard in our Security Policy, and must be deleted on request or termination.

Changes and deprecation

We may change or deprecate endpoints. Breaking changes are announced with a reasonable migration window except where a security fix requires immediate action.

Suspension

Access may be suspended immediately for security risk, abuse, or excessive load.

Changes to this document

We may update this document as our services, technology, and legal obligations evolve. Material changes are published with a new version number, an updated effective date, and a summary of changes in the version history below.

Continued use of our websites, products, services, experiences, or communities after an update takes effect constitutes acceptance of the current version.

Contact

Questions about this API Terms may be sent to our legal and compliance contact through the contact form on this site. Please reference the document title and version number.

  • Legal & compliance requests: use the Contact Legal link on this page
  • Privacy and data rights requests: see the Consumer Privacy Rights policy
  • Accessibility accommodations: see the Accessibility Statement

Review notice

This document is a high-quality draft template prepared for review. It is not legal advice and no guarantee of compliance is made or implied. Final responsibility for legal sufficiency rests with the organization's licensed legal counsel.

Building on our API?

Request credentials and we will scope the access your integration needs.

Related policies