API Documentation
Integrate VentureAI's powerful analysis and deal sourcing capabilities into your own applications.
Quick Start
Step 1:
Generate an API key from your Settings page
Step 2:
Include the key in the X-API-Key header for all requests
Step 3:
Make POST/GET requests to the endpoints below
Authentication
All API requests must include your API key in the request header:
X-API-Key: vai_your_api_key_hereRate Limits:
1,000 requests per month per API key
POST
Venture Analysis
/apiAdvisorAnalyze a startup idea and get AI-powered insights with probability scores.
Request Body:
{
"venture_name": "string (required)",
"industry": "string (required)",
"stage": "string (optional: idea, prototype, launched, scaling)",
"vision_mission": "string (required)",
"target_audience": "string (optional)",
"key_differentiator": "string (optional)"
}Example Request:
curl -X POST https://your-app.base44.io/api/apiAdvisor \
-H "X-API-Key: vai_your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"venture_name": "AI SaaS Platform",
"industry": "Software",
"stage": "idea",
"vision_mission": "Revolutionize business automation",
"target_audience": "SMBs",
"key_differentiator": "10x faster than competitors"
}'POST
Investor Sourcing
/apiDealSourcingFind matching investors for your startup based on criteria.
Request Body:
{
"venture_name": "string (required)",
"industry": "string (required)",
"stage": "string (optional)",
"funding_target": "string (optional)",
"geography": "string (optional)"
}Example Request:
curl -X POST https://your-app.base44.io/api/apiDealSourcing \
-H "X-API-Key: vai_your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"venture_name": "TechStartup",
"industry": "FinTech",
"stage": "seed",
"funding_target": "$2M",
"geography": "North America"
}'GET
Validate API Key
/validateApiKeyTest if your API key is valid and check remaining rate limits.
Example Request:
curl -X GET https://your-app.base44.io/api/validateApiKey \ -H "X-API-Key: vai_your_api_key_here"
Best Practices
- •Store your API key securely - never commit it to public repositories
- •Handle rate limit errors (429 status) gracefully with exponential backoff
- •Cache results when possible to reduce API calls
- •Use meaningful names for your API keys to track usage by application