FAQ
Questions about Findexar? We’ve got answers.
Learn how the platform handles billing, credits, support, and multi-project deployments for your ChatGPT apps.
What is Findexar?
Findexar is a SaaS operations layer for ChatGPT apps and agents. We provide organization management, subscription plans, user sign-up and management, internal team support, and revenue/cost tracking so you can launch...
Who is Findexar for?
We built Findexar for ChatGPT creators, MCP builders, and internal teams who want to monetize or manage usage of their AI apps. Whether you’re publishing a public agent or running an internal automation, Findexar...
How do subscriptions and credits work?
You create free, paid, or internal plans inside Findexar. Each plan defines monthly credits and overage rules for your end users (engaged-user limits only apply to those end-user plans). When your ChatGPT app invokes...
Does Findexar support internal team usage?
Yes. You can create Internal Team Plans that bypass public billing and let you onboard employees or beta testers. The platform still tracks their activity, credits, and support requests, so you get the same operational...
How does Stripe Connect work in Findexar?
Connect your organization to Stripe once, and Findexar uses your platform account for creator subscriptions (always live keys) while automatically routing end-user payments through the correct environment (live for...
Can I track downstream usage or MCP calls?
Absolutely. Findexar logs every MCP invocation, how many credits were consumed, which downstream connector was used, and which user initiated the call. Your dashboard displays daily usage charts, per-project breakdowns,...
How does support work?
Support functionality is coming soon. You can already reach us via the form on the Support page (emails support@findexar.com), and we’re rolling out the Support GPT + ticketing experience shortly.
What about multiple projects or deployments?
Each organization can create multiple projects with isolated deployments. The `production` deployment always runs against live Stripe keys, while every other deployment is treated as a sandbox/test environment...