# API Terms of Use (v1)

**Effective:** upon publication · **Applies to:** every use of the Creator Guard API
by your account from publication on — live keys, test keys, webhooks, OAuth apps and
the client libraries — in addition to the terms you accepted for your account.

## In plain words (summary — the numbered sections govern)

The API is a second door into the same platform: everything your Account Terms say
about creators, leads, offers, fees and data applies to what you do through it. Keep
your keys secret; whatever happens with your keys is your responsibility, and a key
that leaks is revoked at once. Stay within the published limits and do not try to
get around them. Use creator data only for the placement it was shared for — no
scraping, no reselling, no catalogues, no AI training. An app a creator connects must
show her who you are and must never speak for her. The API is in beta: the published
service levels are targets, not guarantees, and the versioning rules on
docs.creator-guard.com are the ones we keep. API access is free. Changes to these terms
that are worse for you take effect 30 days after we publish them. If you abuse the API
we can switch your access off.

## 1. Definitions and document hierarchy

1. **"API"** means the Creator Guard platform API at `https://api.creator-guard.com/v1`
   and its later major versions, including the sandbox reached with test keys,
   webhooks we send to your servers, the OAuth authorization server at
   `https://app.creator-guard.com`, the client libraries and collections we publish,
   and the documentation at docs.creator-guard.com (the **"Docs"**).
2. **"Account Terms"** means the terms your account accepted on the Platform: the
   Referrer Terms for referral partner accounts; the Agency Platform Terms and the
   Placement Warranty Terms for agency accounts. Capitalized terms not defined here
   have the meaning given there.
3. **"Key"** means an API key (`cg_live_…` or `cg_test_…`), a webhook signing secret
   (`whsec_…`), an OAuth client secret, and any OAuth access or refresh token issued
   to your app. **"Creator Data"** means any information about a Creator that you send
   to or receive from the API.
4. **Hierarchy.** These API Terms supplement the Account Terms and do not replace
   them. For keys, limits, versioning, the sandbox, webhooks and OAuth apps these API
   Terms prevail. For everything else — leads, offers, fees, Commissions, the
   evaluation license, conduct, anti-circumvention and the use of Creator Data — the
   Account Terms prevail; for placement remedies the Placement Warranty Terms
   prevail. Where these API Terms add a restriction on top of the Account Terms, both
   apply. On data protection, the data protection addendum for API partners
   (published in the Docs) prevails once it is concluded.
5. The Docs describe how the API works and the limits in effect. Where the Docs and
   these API Terms differ on a legal point, these API Terms prevail.

## 2. Who may use the API

1. Creator Guard, operated by Creator Guard LLC (1209 Mountain Road Pl NE #11622,
   Albuquerque, NM 87110, USA), grants your account a non-exclusive,
   non-transferable, revocable right to use the API for the duration of your account,
   solely to perform the Account Terms: as a referral partner to submit and manage
   your own leads and see your Commissions; as an agency to receive and handle Offers
   and Reservations; and, through an OAuth app, to act for a Creator who connected
   your app, within the scopes she allowed.
2. Access follows your account. Keys work only while your account is approved; while
   it is pending or disabled, the API refuses your requests.
3. You may not sublicense, sell, rent or otherwise give access to the API, a Key, or
   API output to anyone outside your organization. Contractors who build or run your
   integration may use your Keys on your behalf; you are responsible for them as for
   yourself, and the limits of the Account Terms on sharing Creator Data apply to
   them unchanged.

## 3. Keys and credentials

1. **Secrecy.** Keep every Key secret: on servers only, never in a browser, a mobile
   or desktop app you ship, a public repository, a support message, or a chat. A Key
   is sent only to `https://api.creator-guard.com` (an OAuth secret or token only to
   the endpoints the Docs name for it).
2. **Responsibility.** Every request made with one of your Keys is treated as made by
   your account, whoever sent it. You are responsible for everything done with your
   Keys until they are revoked.
3. **Report a leak.** If a Key may have been exposed, revoke or roll it at once (in
   the portal or with the API) and tell us without undue delay at
   info@creator-guard.com, naming the Key's prefix — never the full Key.
4. **Our right to revoke.** We may revoke any Key immediately and without asking
   first when it is reported to us as public — by you, by anyone else, or by an
   automated secret scanner such as GitHub's — or when we reasonably believe it is
   compromised or used against these API Terms. A revoked Key cannot be re-enabled;
   you create a new one. We tell your account's contact address when we revoke a
   leaked Key.
5. Use the security features the Docs offer where they fit your setup (scopes, IP
   allowlists, expiry dates, the key policy). Give each Key only the scopes it needs.

## 4. Team members and roles

1. Your account may have several members with the roles the Docs describe (owner,
   admin, developer, viewer). You decide who becomes a member and with which role,
   and you are responsible for what every member and every Key a member created does.
2. Remove a member without delay when the person leaves your organization or no
   longer needs access. Removing a member or lowering their role revokes the Keys and
   rotates the secrets the Docs list for that case; it does not undo what was done
   before.
3. A login belongs to one person. Do not share logins or second factors between
   people.

## 5. Permitted and prohibited use

1. **Permitted.** You may use the API to automate what your Account Terms allow you to
   do in the portal, for your own account and your own leads, Offers and Reservations.
2. **Prohibited.** You must not, and must not let anyone else:
   (a) **scrape or harvest** — use the API, the portal or the hosted pages to collect
   data beyond what your account needs for its own leads, Offers and Reservations, or
   to compile lists, databases or "catalogues" of Creators, agencies or referral
   partners;
   (b) **probe for other accounts' creators** — submit handles you do not genuinely
   represent to find out whether another account already submitted a Creator, or
   otherwise try to learn which account referred a Creator or which agencies saw her;
   (c) **circumvent limits** — exceed or evade the rate limits, the concurrency
   limits, the duplicate budget or any other limit, for example by spreading load
   over several Keys or accounts, rotating IP addresses, or retrying refused requests
   in a tight loop;
   (d) **resell or share access** — give access to the API, a Key or API output to a
   third party, or offer a service that lets others use the API through you;
   (e) **use Creator Data beyond its purpose** — keep, combine, enrich, publish,
   forward, advertise with, or use for training AI models or creating AI-generated
   likenesses, any Creator Data you receive, beyond what the Account Terms allow;
   (f) **impersonate** — build an OAuth app, a hosted flow or any screen that presents
   itself as the Creator, as Creator Guard, or as another account, or that collects a
   Creator's Creator Guard password;
   (g) **record a Creator's decisions for her** — give, or route around the block on,
   her consent, her 18+ confirmation or her acceptance of the Creator Terms through
   an app of the account that referred her. These decisions are made only on Creator
   Guard's own pages, and the API refuses them through the referring account's apps
   (`403 referrer_app_not_allowed`). Using another account's app, a contractor's app
   or any other workaround for that purpose is a material breach;
   (h) **attack the API** — run load or denial-of-service tests, send automated
   vulnerability scans with large volumes of traffic, try to reach data of another
   account, or bypass authentication, scopes or IP allowlists;
   (i) **put real Creator Data into the sandbox** — test keys are for made-up data
   only;
   (j) send data you are not allowed to send, or content that is unlawful, or put
   identity documents, passwords, payment details or explicit material into free-text
   fields.
3. Prohibited use under Section 5(2)(b), (e), (f) or (g) is also a breach of the
   Account Terms and is sanctioned under them.

## 6. OAuth apps

1. You may register OAuth apps through which a Creator can connect her Creator Guard
   account to your service. An app may act for her only within the scopes she
   allowed, and only while the relationship the Docs require (you referred her, or
   you hold a paid Reservation for her) exists.
2. Your app must name your organization truthfully, link to your own privacy policy,
   and use a name and logo that do not suggest it is Creator Guard or someone else.
3. Before your app records a decision of hers that the Docs allow it to record, show
   her the current text we provide, unchanged, and send its version with her answer.
   Her withdrawal of consent must always be possible through your app.
4. When she disconnects your app, or the relationship ends and we revoke her grant,
   stop acting for her. What you hold about her from that point is governed by the
   Account Terms and Section 9.

## 7. Limits, fair use and throttling

1. The limits in effect for your account are those published in the Docs (rate
   limits per Key, concurrency, uploads, webhook replays, and the duplicate budget of
   the account) or shown by `GET /v1/me`. Test keys have the reduced limits the Docs
   name. We may set different limits for your account; the API shows them.
2. **Fair use.** Use the API with reasonable restraint: no requests your integration
   does not need, no polling where events or webhooks serve, and tell us in advance
   before a large import.
3. We may throttle, queue or refuse requests — including with `429` answers — to
   protect the API, other accounts or Creators, and may lower your limits if your use
   strains the API or breaches Section 5. Where it is practical we tell you first.

## 8. Beta, service levels, changes and deprecation

1. **Beta.** The Platform and the API are in beta. Features arrive often. The
   versioning rules published in the Docs ("Versioning") are binding on us.
2. **Service levels are targets.** The service levels published in the Docs (today:
   99.5 % monthly availability of `/v1` in live mode, p95 under 500 ms for
   single-resource reads, p95 under 60 seconds to the first webhook delivery attempt)
   are targets we run the API against and measure. They are not a guarantee, and no
   service credits or other remedies attach to them, unless we agree otherwise in
   writing.
3. **Changes within a major version.** A change that could break a working
   integration never ships inside a major version (`/v1`); it ships as a new major.
   We may add to a major version at any time (fields, endpoints, scopes, error codes,
   events); read answers tolerantly as the Docs describe. Stricter validation within
   a major version — rejecting input the API cannot handle well, or returning `null`
   in a field we may no longer show — ships as a minor release, is effective at
   release, and is described in the changelog under "Tightened"; there is no separate
   e-mail.
4. **Retiring a major version.** When a new major version goes live, the previous one
   stops on the same day: its requests answer `410 version_sunset`. There is no
   notice period; watch the changelog.
5. We may change, suspend or discontinue any part of the API, the sandbox, the client
   libraries or the Docs, within the rules of this Section.

## 9. Data protection

1. **Roles.** Each party's role for the Creator Data exchanged through the API follows
   the Account Terms and, once concluded, the data protection addendum for API
   partners. Until then, and as the working basis of that addendum, you and we each act
   as an independent controller for the Creator Data each of us holds: you for what you
   collect and keep in your systems, we for what we receive and process for the
   Platform.
2. **Your own systems.** Protect Creator Data in your systems with measures
   appropriate to its sensitivity — a Creator's age and content categories can reveal
   information about her sex life. Webhook endpoints must use HTTPS and check our
   signature as the Docs describe.
3. **Agencies.** Creator Data an agency receives through the API or webhooks is
   licensed only to evaluate and complete a placement (Agency Platform Terms,
   Section 5). The Creator's name and contact details are released only after we
   confirm receipt of the Placement Fee; before that the API shows her creator number
   only (`creator_name` is `null`). Delete what you received about a Creator within
   30 days after an Offer ends without your payment for her, and within 30 days after
   we tell you she withdrew her consent (the event `offer.consent_revoked`), unless you
   completed a placement with her; after Contact Release, Section 9 of the Agency
   Platform Terms governs.
4. **Referral partners.** Send only Creator Data the Creator knows you are sending
   (Referrer Terms, Sections 2 and 6), and forward a Creator's request about our copy
   of her data to info@creator-guard.com with her creator number.
5. **OAuth apps.** Creator Data your app receives because a Creator connected it is
   processed under your own privacy policy, which your app names; for that copy you are
   an independent controller.
6. **What we log.** We keep a request log, usage statistics and an audit trail of
   changes to your account, for the periods published in the Docs ("Data retention"),
   and use them to run, secure and support the API.

## 10. Security

1. Report a vulnerability you find in the API, the Platform or the Docs to
   info@creator-guard.com with the subject "Security", following our vulnerability
   disclosure policy at https://docs.creator-guard.com/security/ (machine-readable
   contact: https://docs.creator-guard.com/.well-known/security.txt).
2. Test only with your own account, your own test data and, where possible, test
   keys. Never read, change or delete data that is not yours; if you see someone
   else's data, stop and report it. Do not make an issue public before we fixed it.
3. Tell us without undue delay of any security incident in your systems that affects
   Creator Data received through the API or a Key — without undue delay and at the
   latest within 72 hours after you become aware of it, at info@creator-guard.com.

## 11. Suspension and termination

1. We may suspend your API access, or parts of it, immediately and without prior
   notice where we reasonably believe it is needed to stop a breach of Section 3, 5 or
   6, to protect Creators, other accounts or the API, or where the law requires it.
   Other breaches follow the sanctions ladder of the Account Terms.
2. **Effects.** On suspension or termination we may revoke your Keys, disable your
   webhook endpoints, disable or delete your OAuth apps (which ends the Creators'
   connections to them) and refuse further requests. Suspension of your account under
   the Account Terms suspends your API access as well.
3. You may stop using the API at any time by revoking your Keys and deleting your
   webhook endpoints and OAuth apps. Closing your account follows the Account Terms.
4. After the end of your access, your duties under the Account Terms and Section 9 —
   in particular the deletion of Creator Data — continue.

## 12. Fees

Access to the API is free of charge unless we agree otherwise with you in writing.
Placement Fees, Commissions and other amounts remain governed by the Account Terms.

## 13. Client libraries and documentation

1. The client libraries and collections we publish are generated from the published
   contract. They are licensed under the MIT License, as stated in the package.
2. The code samples in the Docs are licensed under the MIT License as well; you may
   copy them into your integration.
3. The MIT License covers the code only. It grants no right to use the API, which
   these API Terms govern, and no right to the Creator Guard name or logo.

## 14. Warranties and liability

1. The API, the sandbox, the client libraries and the Docs are provided "as is" and
   "as available". To the maximum extent permitted by law, we give no warranty that
   they are uninterrupted, error-free or fit for a particular purpose.
2. Liability arising from or related to the API is part of, and does not add to, the
   liability cap of your Account Terms; no liability for indirect or consequential
   loss, including lost data or revenue caused by an outage, a throttled or refused
   request, a revoked Key or a retired major version.
3. **Indemnity.** You indemnify us — and any affected Creator — against claims arising
   from your integration, your OAuth app, the use of your Keys, or your breach of
   these API Terms.

## 15. Changes to these API Terms

1. **Versioned terms.** We publish each new version on the Platform, where
   `GET /v1/agreements` shows it, and announce it with the event `agreement.published`
   and in the changelog in the Docs.
2. **30 days' notice for adverse changes.** A material change that is adverse to you
   takes effect 30 days after we publish it. Other changes take effect on publication.
3. **Immediate changes.** A change that is legally required — by law, a court or an
   authority — or that is needed for the security of the API or to stop abuse takes
   effect on publication.
4. **Acceptance.** Your account accepts these API Terms once, by an owner or admin, in
   the portal or with `POST /v1/agreements/api_terms/accept`. Any accepted version
   counts, and continued use of the API after a new version takes effect constitutes
   acceptance — unless we mark a new version as "re-acceptance required"; then live
   writes need that version from the day it takes effect.
5. **The API contract is not changed through this Section.** Changes to the API
   itself (endpoints, fields, errors, limits) follow the versioning policy in the Docs
   (Section 8).

## 16. General

Governing law: State of New Mexico; exclusive venue the state and federal courts in
Bernalillo County, New Mexico. Notices: via the Platform or registered e-mail (to us:
info@creator-guard.com), effective when sent; operational notices about Keys, limits
and the API also through the API's events and the changelog. We may assign to a
successor of the Platform; you may not assign without consent. No waiver by
non-enforcement. Force majeure excuses delay, not amounts due. Sections 3(2), 5, 9, 11(4),
14 and this section survive termination. You consent to electronic contracting and
records; the request log, the audit trail and other Platform logs are admissible
business records. Headings are for convenience; "including" means "including without
limitation"; the English version prevails over any translation. Severability applies —
an unenforceable provision is replaced by the enforceable rule closest to its intent.
