Key Features
Capability reference for Agentsyx Creator—use this when you want a checklist of what the platform covers. For narrative and positioning, see What is Agentsyx?.
Billing & Subscriptions
Stripe Connect Integration
- Connect your Stripe account to handle payments
- Create subscription plans (free, paid, internal team)
- Automatic billing and invoice management
- Support for credit-based and usage-based pricing
Subscription Management
- End users can upgrade, downgrade, or cancel subscriptions
- Automatic credit allocation based on plan
- Overage handling and notifications
- Grace period management
User Authentication
OAuth 2.0 Integration
- User sign-up via Clerk
- User login within supported AI hosts (OAuth in the host UI where applicable)
- Secure authentication and session management
- Automatic user context injection
API Key Support
- Generate API keys for programmatic access
- Manage and revoke keys
- Track API usage per key
Tool Mapping & Pricing
Flexible Tool Mapping
- Map downstream tools to upstream tools
- Set credit prices for each tool
- Support for multiple downstream connectors
- Automatic tool discovery and selection
Credit System
- Credit-based pricing model
- Track credits per user and organization
- Automatic credit deduction on tool usage
- Credit allocation based on subscription plans
Creator workspace (org, project, deployment)
Your Agentsyx Creator account is organized as a single workspace hierarchy—not a “multi-tenant” product in the sense of many unrelated tenants sharing one Creator org.
- Organization — Top level for your builder identity: billing, Stripe, org-wide settings, and how you publish MCP apps.
- Projects — Group connectors, upstream/downstream configuration, and apps; you can run multiple projects under one org.
- Deployments — Environments inside a project (for example production vs preview) with their own connector endpoints and configuration.
Roles (Creator and collaborators)
- Org admin / Creator — Full control over the org, projects, connectors, plans, and publishing.
- Superuser — Broader operational permissions within the org where you enable them.
- Team member — Collaborator access scoped to specific projects you assign (people who help you build, not your paying MCP customers).
- End user — Someone who subscribes and uses apps on www.agentsyx.com; they do not log into Creator.
User organizations and teams (customer side)
Multi-tenant organization behavior—end-user teams with their own org, roles, and shared agents/apps on the customer surface—is separate from your Creator org/project tree and is evolving on the roadmap. See A6: B2B (future).
MCP Apps (embedded UI)
Widgets over standard MCP
- MCP Apps expose tools plus HTML (or similar) UI through
resources/read, with_metafor linking tools to resource URIs and for host embedding (including CSP-style rules where the host supports them) - MCP-capable hosts can embed that UI (for example in an iframe) while the model continues to use
tools/call; widget code typically invokes tools via the host’scallServerTool(or equivalent) surface - Use for subscription flows, payments, dashboards, or any custom surface tied to your tools—without a separate proprietary “bridge” protocol
For terminology and protocol detail, see What is MCP? and MCP App (widgets) metadata.
Usage Tracking & Analytics
Real-Time Usage Tracking
- Track tool usage per user
- Monitor credit consumption
- View usage history and trends
- Export usage data for analysis
Analytics Dashboard
- Creator dashboard for managing your apps
- User dashboard for managing subscriptions
- Usage analytics and insights
- Billing and revenue tracking
Connector Management
Downstream Connectors
- Connect Zapier, Make, n8n MCP servers
- Connect MCP App servers (tools + widget UI via
resources/read) and other custom MCP servers - Connect any MCP-compatible service
- Manage multiple downstream connectors
Upstream Connectors
- Create upstream MCP endpoints for MCP-capable AI hosts
- Select and configure tools from downstream connectors
- Set pricing and usage limits
- Register or connect your upstream URL in each host’s flow—for example OpenAI ChatGPT (GPT + MCP)
Support & Documentation
Documentation
- Step-by-step guides for common tasks
- API reference and examples
- Troubleshooting guides
- Best practices and tips
Support Tools
- User management and support
- Issue tracking and resolution
- Community resources
- Direct support channels
Next Steps
- Get started with Getting Started Guide
- Explore How-To Guides for step-by-step instructions