Frequently Asked Questions
Everything you need to know about our API
Records include ingredient names, synonyms, cosmetic functions and identifiers where available. Comedogenicity and irritancy ratings are nullable and coverage varies by field. Test representative ingredients from your own catalog and consult the live OpenAPI contract before integration. The API provides data for software, not clinical diagnosis.
Severity labels are derived from stored comedogenicity and irritancy values. Missing ratings remain null; the legacy severity label alone does not distinguish an unassessed ingredient from a low-scored one. Check the underlying fields and show missing data explicitly. Ratings do not predict an individual's response to a finished product.
Yes. The API is intended for commercial products: mobile apps, e-commerce, internal tools, and SaaS. Plans, rate limits, and pricing are described on our pricing page (subscriptions plus usage-style options). Enterprise customers can discuss custom terms, SLAs, and integrations on our contact page.
We target high availability for production use and document SLA-style expectations with paid tiers where applicable. Infrastructure is monitored around the clock; status and incidents are communicated through our status page when available. Exact numbers depend on your plan—ask sales for Enterprise guarantees.
Yes. Try REST without a key: 5 requests per IP per 24-hour window, up to 3 search results without pagination, or 5 names per analysis. The allowance is shared across endpoints. After the second request, responses include a registration link. Register for an API key and 100 welcome credits to continue with full access. Hosted MCP requires a key.
Response time depends on your region, network, endpoint, payload size, and current service load. Test the production API from the regions your application serves and contact us if you need plan-specific performance or availability terms.
Any language that can send HTTPS requests works. Try REST without a key or use a Bearer token for full access. Our published SDKs 1.0.0 support ingredient and product search, lookup, analysis and optional API keys: JavaScript/TypeScript on npm (https://www.npmjs.com/package/dermalytics) and Python on PyPI (https://pypi.org/project/dermalytics/). AI agents can use the hosted MCP server at https://api.dermalytics.dev/mcp with docs at https://api.dermalytics.dev/v1/mcp/docs. For interactive API tests, use the hosted Swagger UI at https://api.dermalytics.dev/docs. The REST contract is defined in OpenAPI 3 at https://api.dermalytics.dev/openapi.json. Guides and examples are on our /docs page.
Coverage and records can change over time. We do not promise a fixed refresh schedule for every ingredient or product. Validate the fields your application relies on, and contact us to discuss update requirements for your integration.
Still have questions? We're here to help.
Contact Support