​
Revenue Model

When Pro users utilize your published API, you earn credits based on their usage:
  • You earn $0.05 per million tokens when Pro users use your published APIs
  • Enterprise usage provides further revenue opportunities

​
Publishing Process

1

Design & Test

First design a private API at https://critique-labs.ai/design:
  • Provide an initial prompt to design the API (a chat-like interface will be available soon)
  • Review the API inputs and make sure they make sense for the API you want to create
  • Check the generated endpoint stub (i.e., /my-cool-api) and make sure it looks right. Note that sometimes a unique identifier is added to the end of the stub (i.e., /my-cool-api/af4922). This is fine and expected.
  • IMPORTANT: Check the configuration instructions and make sure you cover all the cases you want to support as well as the cases you don’t want to support
  • MOST IMPORTANT: Test the API to ensure it works as expected. If you don’t like the output, you can edit the configuration instructions and test again.
2

Complete Publication Form

Required information:
  • API Title
  • Description
  • Project URL (optional)
  • Category selection
  • Tags (recommended)
3

Review & Confirm

Review:
  • API documentation
  • Usage examples
  • Integration guides
  • Terms of service
4

Monitor & Maintain

Track:
  • Usage statistics
  • User feedback
  • Performance metrics
  • Revenue generation
  • Create new versions of your API if needed

​
API Visibility

Your published API will be showcased in the marketplace with:

Basic Info

  • API title and description
  • Your username as publisher
  • Last update date
  • Category and tags

Performance Metrics

  • Usage statistics
  • Average response time
  • Active user count
  • User ratings

​
API Usage

Your API listing includes three main sections for users to interact with:

​
1. General API Information

  • API Title and Description
  • Input Request and Output Response Formats
  • Categories and Tags
  • Project URL (optional)
  • Total Unique Users who have used your API
  • Total Calls made on your API

​
2. Code Samples

Example implementations will automatically be generated for your API in:
  • JavaScript
  • Python
  • cURL

​
3. Test Endpoint

An interactive environment where users can:
  • Test your API with sample inputs
  • Validate responses
  • Check latency and average tokens per call

​
Best Practices

Clear Description

Write concise but detailed explanations of your API’s functionality and use cases

Proper Documentation

Include comprehensive guides, examples, and edge cases

Appropriate Tags

Add relevant tags to improve marketplace discoverability

Regular Updates

Maintain and improve your API based on user feedback and usage patterns

​
Support

For questions about the publishing process:

​
Terms of Service

Before publishing, review our: