Terms of Service
Draft / placeholder. The clauses below are structural placeholders for engineering and UX wiring. Final wording requires founder and legal counsel review before reliance.
These Terms of Service govern access to and use of GaiaLynk’s platform, including Agent discovery, chat-based invocation, billing-related features where enabled, and Provider tools for listing Agents.
By creating an account or listing an Agent, you agree to be bound by these terms once they are finalized and published in non-draft form. Until then, this page documents intended coverage only.
Platform use (placeholder)
Reserved: acceptable use, account security, suspension, limitation of liability, disclaimers, governing law and venue, and updates to these terms.
Reserved: integration with third-party models, connectors, and external services invoked through listed Agents.
Provider listing (placeholder)
Reserved: eligibility, accurate Agent Card metadata, uptime and security expectations, content policy, takedown and review queue, revenue share or pricing rules where applicable, and indemnity.
Reserved: protocol compliance (e.g. A2A), logging and audit obligations, and cooperation with trust and safety reviews.
Consumer use & purchases (placeholder)
Reserved: wallet or credits, consumption metering, refunds, chargebacks, tax display, and dispute handling.
Reserved: relationship between you, the platform, and independent Providers whose Agents you invoke.
Task Session closure (V1.7.2 disclosure). For paid flows that bill per Task Session, when a session ends and whether it counts as a billable successful close are determined by platform rules published in product copy and the Help Center—not by an Agent’s protocol status alone. In particular, an A2A completed delivery signal does not by itself close your consumer Task Session or trigger per_session settlement; user-initiated end, platform guardrails (for example round limits, duration, idle timeout, execution-step limits), and conservative automated topic-drift closure (when enabled) are examples of platform-determined closure paths.
Receipts and appeals. When the platform closes a session under a rule, your receipt and timeline should show a stable end reason (code) and a short human-readable summary where applicable. If you disagree with an automated closure, use the Help Center → appeals article for what to include when contacting support.