API Overview
Base URL
Section titled “Base URL”https://mcll3bnfubyazfg6wekv3xc6fi0dgpyk.lambda-url.us-east-1.on.awsRequest format
Section titled “Request format”All POST endpoints accept JSON request bodies. Set the Content-Type: application/json header.
Authentication
Section titled “Authentication”Include your API key in the X-API-Key header:
curl -X POST https://mcll3bnfubyazfg6wekv3xc6fi0dgpyk.lambda-url.us-east-1.on.aws/identify_clothing \ -H "X-API-Key: ss_your_key_here" \ -H "Content-Type: application/json" \ -d '{"image_url": "https://example.com/outfit.jpg"}'Response format
Section titled “Response format”All responses return JSON. Successful responses return a 200 status code with the endpoint-specific payload.
Error handling
Section titled “Error handling”Errors return a JSON object with an error field:
{ "error": "Description of what went wrong"}Status codes
Section titled “Status codes”| Code | Meaning |
|---|---|
200 | Success |
400 | Bad request — missing or invalid parameters |
401 | Unauthorized — missing API key |
403 | Forbidden — invalid API key |
404 | Not found — endpoint doesn’t exist |
500 | Internal server error |
Rate limits
Section titled “Rate limits”There are currently no hard rate limits, but please be reasonable with usage. Image generation endpoints (/generate_image, /style_me) are compute-intensive and take 10-30 seconds per request.
Endpoints
Section titled “Endpoints”| Endpoint | Method | Description |
|---|---|---|
/generate_image | POST | Generate virtual try-on images |
/identify_clothing | POST | Identify clothing items in an image |
/style_me | POST | Get personalized outfit recommendations |
/usage | GET | View API usage statistics |