> ## Documentation Index
> Fetch the complete documentation index at: https://docs.curvelabs.org/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Answers to common ThinkFeel API questions.

<AccordionGroup>
  <Accordion title="How much does the API cost during beta?">
    Beta access uses pricing close to the cost of the underlying models. This keeps beta usage fair. Curve Labs may introduce
    a free tier in the future based on community feedback.
  </Accordion>

  <Accordion title="How are personas created?">
    During your onboarding call, Curve Labs works with you to design a custom persona tailored to your use case. The team
    collaboratively defines personality traits, communication style, and behavioral guidelines that match your product needs.
  </Accordion>

  <Accordion title="Is conversation history stored on Curve Labs servers?">
    No. The API is stateless. You maintain full control over conversation history and manage it on your end.
  </Accordion>

  <Accordion title="Should I use includeVariations in production?">
    For most production use cases, the default response is sufficient. Enable `includeVariations: true` when you want to show
    users alternative response options or inspect other replies the AI generated.
  </Accordion>

  <Accordion title="Can I refine my persona after onboarding?">
    Yes. Curve Labs encourages ongoing refinement. Contact support to adjust your persona based on real-world usage and
    feedback.
  </Accordion>

  <Accordion title="What model powers the API?">
    You do not choose a model directly. Use your assigned persona ID as `personaId`, or as `model` on the OpenAI-compatible
    endpoint. Curve Labs keeps the request format stable as backend models evolve.
  </Accordion>

  <Accordion title="Can I get higher rate limits?">
    Yes. Contact Curve Labs through [support](https://curvelabs.org/support) with your use case and expected volume. Higher
    limits are available for production-level projects.
  </Accordion>
</AccordionGroup>