# Green Monkey Hair Intelligence API > Governed, non-medical hair-wellness intelligence that AI agents can purchase per request using USDC via x402 on Base Mainnet. Website: https://api-greenmonkey.org OpenAPI: https://api-greenmonkey.org/openapi.json Status: https://api-greenmonkey.org/status Provider: Green Monkey Club AG Network: Base Mainnet, CAIP-2 eip155:8453 Payment asset: USDC Payment protocol: x402 V2 Payment scheme: exact ## Free endpoint POST https://api-greenmonkey.org/v1/safety-check Purpose: Evaluate deterministic exclusion criteria and determine whether an outside-only track or an inside-and-outside track may be considered. Price: Free. ## Paid API 1 POST https://api-greenmonkey.org/v1/recommend Name: Product Recommendation Intelligence Price: 0.10 USDC per successful request. Purpose: Analyse the submitted hair and safety profile, apply deterministic safety and product-fit rules, and return the most suitable Green Monkey offer. Expected output: - safety decision - permitted track - selected product - recommendation rationale - direct purchase URL - non-medical disclosure ## Paid API 2 POST https://api-greenmonkey.org/v1/hair-transform-90/build Name: Personalised 90-Day Routine Builder Price: 0.08 USDC per successful request. Purpose: Create a governed 12-week hair-wellness routine with day 30, 60 and 90 checkpoints. Execution: 1. Deterministic safety and eligibility rules execute first. 2. A Routine Agent personalises approved coaching language. 3. A separate QA Agent checks the result. 4. Safety rules, track, products, purchase URLs and week structure cannot be changed by AI. 5. A deterministic fallback is returned if AI or QA fails. ## Profile example { "age_group": "30_44", "pregnancy": false, "breastfeeding": false, "medication_context": "no", "multiple_supplements": false, "iron_status_concern": false, "urgent_hair_or_scalp_red_flag": false, "wants_inside_support": true, "hair_pattern": "wavy", "primary_goal": "volume", "country_code": "DE" } ## x402 interaction 1. Send the POST request without a payment signature. 2. Read the HTTP 402 response and PAYMENT-REQUIRED header. 3. Authorise the exact USDC payment using an x402-compatible client. 4. Retry the request using the PAYMENT-SIGNATURE header. 5. Read the API response and PAYMENT-RESPONSE settlement header. ## Safety limits The API provides non-medical hair-wellness information. It does not: - diagnose a condition - prescribe treatment - replace a qualified healthcare professional - guarantee an outcome - permit an AI model to override deterministic safety exclusions