FAQ
Frequently asked questions
Clear answers about wallet credit, usage, subscriptions, and how Tycoon charges for work.
Our API is legacy REST with no OpenAPI spec and messy handlers. Can this even start?
Yes, with a bootstrap phase. AI CTO introspects your API via a crawler: every route in your router, every response captured from running traffic, every status code observed, every query parameter inferred. Assembles a best-guess OpenAPI spec (70-85% accurate) that you then refine. Takes 1-2 weeks of review to get to production-quality, but it's front-loaded — once the spec exists, the automated workflow takes over. Most teams report that the bootstrap alone caught 15-30 inconsistencies they didn't know about.
We use GraphQL, not REST. Does this still apply?
Yes, different tooling. GraphQL schemas are already introspectable via SDL. AI CTO uses your schema + @deprecated directives + operation definitions to drive the docs. Testing moves from curl samples to operation samples with expected responses. Docs platforms for GraphQL (GraphQL Inspector, Apollo Studio, Hashnode GraphQL) integrate the same way. Breaking change detection is actually more accurate for GraphQL because the SDL is typed.
What about internal tools / internal APIs where docs are for engineers, not customers?
Same workflow, different polish level. Internal docs get auto-generated from the spec but skip the prose-writing step (engineers can read the spec fine). Internal endpoints stay in a separate namespace on the docs site (docs.internal.yourcompany.com) with auth gating. The value for internal: new engineers onboard in hours instead of days because the docs are actually complete.
Our API has authentication, webhooks, and async callbacks. Auto-generation misses context for those.
Auto-generation handles the schema; context is layered on top. AI Head of Content maintains the 'conceptual docs' (authentication flows, webhook signatures, idempotency rules, rate limits, error handling patterns) as long-form Markdown that references the auto-generated endpoint pages. When endpoints change, the conceptual pages get checked for affected content and flagged for review. Structure: auto-generated = what; human-maintained = why and how.
Can it handle SDKs for multiple languages — keeping Node/Python/Go SDKs in sync with the REST API?
Yes, via code generation + test matrix. OpenAPI Generator produces SDKs from the spec in 40+ languages. AI CTO runs a CI job that: (1) regenerates SDKs on every spec change, (2) runs the test suite for each SDK against the sandbox API, (3) flags SDK breaking changes separately from API breaking changes. SDKs publish to npm/PyPI/Go modules on every API release. Prevents SDK drift — the failure mode where the Python SDK is 6 months behind the API because nobody remembered to regenerate it.