API Usage Guidelines and Limits
Purpose
These guidelines define how developers are expected to use the Sverse Developer Platform API responsibly and sustainably.
The goal is to:
protect the stability of the ecosystem,
ensure fair access for all developers,
and maintain consistent behavior across integrated applications.
These rules apply to all API consumers unless explicitly stated otherwise.
General Usage Principles
Use Only What You Need
Developers should integrate only the API domains required for their application.
Unnecessary or excessive usage of unrelated endpoints is discouraged, as it increases ecosystem load without adding value.
Respect the Shared Ecosystem
Sverse APIs operate within a shared environment.
All applications:
affect platform health,
influence economic signals,
and impact other participants.
Usage patterns should reflect real user intent, not artificial amplification.
Build for Real Users
API calls should represent genuine user actions.
Automated behaviors designed to:
inflate usage,
manipulate asset signals,
or distort marketplace activity are strictly prohibited.
Rate Limits
Rate limits are applied per application and per API domain.
Limits may vary by environment and integration level.
Default Limits
Identity
300 requests
Assets
600 requests
Marketplace
300 requests
Economy
200 requests
Experience
300 requests
Limits are enforced to prevent abuse and ensure consistent performance.
Burst Behavior
Short bursts above the limit may be allowed within controlled thresholds.
Sustained bursts will result in throttling or temporary suspension.
Exceeding Limits
When a rate limit is exceeded:
the API will return an appropriate error response,
requests will be throttled or rejected,
repeated violations may trigger further restrictions.
Developers are responsible for implementing retry and backoff logic.
Quotas and Usage Caps
In addition to rate limits, usage quotas may apply.
Quotas are typically enforced on:
total API calls per day,
transaction volume,
or asset operations.
Quota thresholds are determined by:
application type,
integration scope,
and ecosystem impact.
Quota changes may be requested through the SDeveloper Portal.
Authentication and Credential Usage
API Keys
Each application is issued one or more API keys.
Developers must:
keep keys confidential,
rotate keys periodically,
revoke compromised credentials immediately.
Sharing API keys across applications or teams is not permitted.
Environment Separation
Separate credentials are provided for:
development,
staging,
and production environments.
Production credentials must never be used for testing or experimentation.
Data Access and Responsibility
Developers must access and process only the data required for their application.
User Data
Access only user data explicitly granted through the API
Do not store unnecessary personal data
Comply with applicable privacy and data protection laws
Asset Data
Asset ownership must be verified before usage
Asset usage rules must be respected
Assets must not be duplicated or misrepresented
Marketplace and Economy Constraints
Marketplace-related endpoints are subject to additional scrutiny.
Developers must not:
simulate fake purchases,
manipulate pricing signals,
or generate artificial transaction volume.
Economic interactions must reflect real user intent and behavior.
Violations may result in:
transaction reversal,
revenue suspension,
or permanent access removal.
Monitoring and Enforcement
Sverse continuously monitors API usage patterns.
Monitoring includes:
request frequency,
behavioral anomalies,
economic irregularities,
and policy compliance.
Enforcement actions may include:
warnings,
temporary throttling,
quota reduction,
or access revocation.
Requesting Higher Limits
Developers may request increased limits by providing:
application description,
expected usage patterns,
justification for increased load.
Requests are reviewed manually to ensure ecosystem stability.
Approval is not guaranteed.
Changes to Limits and Policies
API limits and guidelines may evolve as the ecosystem grows.
Changes will be:
communicated in advance when possible,
documented clearly,
versioned when impactful.
Developers are expected to stay informed of updates.
Summary
The Sverse Developer Platform API is designed for long-term collaboration, not uncontrolled access.
By following these guidelines, developers help ensure:
platform reliability,
fair participation,
and sustainable ecosystem growth.
Responsible usage is a prerequisite for building on Sverse.
Last updated