Lumeart markLumeart
Back to Docs
AuthAPI KeySecurity

Authentication And API Keys

How API keys should be passed, separated by environment, and protected.

Header Example

Production APIs should use a consistent bearer token scheme. This example is only a documentation placeholder until the final API contract is confirmed.

bash
curl https://api.guice.ai/v1/tasks \
  -H "Authorization: Bearer $GUICE_API_KEY" \
  -H "Content-Type: application/json"

Key Security

  • Never ship API keys in frontend code, mobile packages, or public repositories.
  • Use separate keys for test and production environments.
  • Add budgets, rate limits, and safety policies for high-risk operations.
Lumeart markLumeart

AI-native creator infrastructure. Create. Connect. Scale.

Developers

Content Policy and Usage Boundaries

Applies to Lumeart public content and creator tools

Content boundary

Lumeart is a general AIGC creation platform. Creators should ensure generated, uploaded, and published content follows local law, platform rules, and project agreements.

Creator responsibility

Users are responsible for ensuring uploaded, generated, and published content is authorized and follows local law, platform rules, and project agreements.

Privacy and data

Lumeart uses project assets, prompt traceability, and render records for the production workflow and does not retain unauthorized browsing history on the public homepage.

Copyright and DMCA

For infringement, impersonation, or unauthorized copyrighted material, contact us to submit a takedown or review request.