GITBEACON — TERMS OF SERVICE (PLAIN-TEXT DIGEST)
Version: v0.1-draft   Effective: 2026-07-09
Canonical (binding) URL: https://api.gitbeacon.dev/terms.txt
Contact: jcislo918@gmail.com

DRAFT — pending legal review. This is a plain-text digest of the full Terms of
Service. The canonical version at the URL above governs and prevails.

1. PARTIES & ACCEPTANCE
   Using the Service — including having software you deploy call the API —
   accepts these Terms. Under UETA / E-SIGN electronic-agent rules, deploying an
   agent = the principal's acceptance; each request and payment binds you.

2. SERVICE DESCRIPTION — INFORMATIONAL ONLY
   gitBeacon sells GitHub trend intelligence: daily LLM-analyzed digests of
   trending new repositories and the raw trending-repo data behind them,
   aggregated from public GitHub data. Output is for information only and is NOT
   investment, engineering, security, or business advice. LLM-generated analysis
   may contain errors; do not rely on it as the sole basis for any decision.

3. DATA SOURCES & FRESHNESS
   Underlying repository data is derived from public GitHub activity. Digests and
   repo rows reflect the most recent daily scan and may be incomplete, delayed,
   or stale; every paid response carries a scanDate/digestDate provenance field so
   you can judge freshness. gitBeacon does not warrant the completeness or accuracy
   of any repository metadata.

4. PAYMENT TERMS
   Paid endpoints are priced per call in USD and settled as USDC via x402 on Base
   Mainnet (eip155:8453). Current per-call prices are published machine-readably at
   https://api.gitbeacon.dev/discovery and https://api.gitbeacon.dev/openapi.json (the binding source of
   truth for prices) — no price table is duplicated here, to avoid drift. The free
   endpoints require no payment. Compute-first / settle-after: you are NOT charged
   for errors. Taxes and network fees are the buyer's. No bundles or subscriptions.

5. REFUND POLICY
   Because the Service settles only after successfully computing a billable answer,
   charges without delivery should not occur; where a settled payment fails to
   deliver, the automated x402 failure path applies. Otherwise all sales are final.

6. PRIVACY
   Request parameters (e.g. language filter, lookback window) are processed to
   produce the response and are not linked to a person. Payment settlement facts
   (payer address, tx hash) may be logged for accounting. gitBeacon does not
   collect owner, registrant, or end-user personal data.

7. ACCEPTABLE USE
   No unlawful use. No circumventing rate limits or payment. Free endpoints are
   rate-limited; abusive traffic may be throttled or blocked. Underlying public
   GitHub data remains subject to GitHub's own terms.

8. AS-IS / NO WARRANTY
   Service and data provided "AS IS" / "AS AVAILABLE", with no warranties of any
   kind. Data may be delayed, wrong, incomplete, or stale. No uptime, latency, or
   continuity guarantee; no SLA.

9. LIMITATION OF LIABILITY
   No liability for indirect, incidental, or consequential damages, or for
   decisions made in reliance on the Service. Total liability capped at fees paid
   to gitBeacon in the prior 30 days.

10. GOVERNING LAW & DISPUTES
    Governed by the laws of the operator's country of establishment (Poland) and
    applicable EU law; disputes before the competent courts there, subject to
    mandatory consumer-protection rights.

11. CHANGES TO TERMS
    We may update these Terms; the version/effective date and canonical URL will
    be revised. Continued use after changes = acceptance.