Skip to main content

Acceptable Use

Draft

Placeholder terms for the development phase. Final acceptable-use terms will be published before the API opens to third parties.

By using the AyakaMods API you agree to:

Downloads​

  • Always fetch files through the API download endpoint (mod-versions/{id}/download) with your key. Do not cache, share, or hotlink a raw storage URL - access must stay revocable.
  • Do not redistribute downloaded files outside your integration's normal install flow.

Rate limits​

  • There is no hard per-key request cap on the read API today. That is fair use, not a free pass: do not hammer the API or parallelize aggressively, and use batch lookups (mod_ids) instead of one request per mod. Keys that cause load problems get throttled or revoked. If hard limits are introduced, they will be documented here.
  • Cache list/detail responses reasonably rather than re-fetching on every frame or view.

Attribution & content​

  • Attribute AyakaMods as the source of mods in your UI.
  • Respect each game's content rules, including NSFW exclusion where set.
  • Respect mod authors' licensing and the takedown/moderation state of any mod.

Keys​

  • Keep your key secret wherever you can (server-side). A key that ships inside a distributable client must be a read-only key issued for that purpose. Never ship a key with write scopes or super-user access. See Keep your key safe.
  • One key per integration. Tell us if your use case or volume changes materially.

Abuse may result in a key being revoked without notice.