Get remote caching status
Check the status of Remote Caching for the authenticated user or team. Returns a JSON-encoded status indicating if Remote Caching is enabled, disabled, or disabled due to usage limits. Implementers should return `enabled` if the authenticated principal is allowed to use the cache, or `disabled` if not. The `over_limit` and `paused` statuses are optional and can be used to indicate usage limits or temporary suspension.
Authorization
bearerToken Bearer token authentication. Pass your authentication token in the Authorization header as Bearer <token>.
For self-hosted implementations, the token format and validation logic is up to the implementer. Common approaches include:
- Static tokens for simple setups
- JWT tokens for stateless authentication
- OAuth2 tokens for integration with identity providers
In: header
Query Parameters
The team identifier to perform the request on behalf of. Used for multi-tenant cache implementations where artifacts are scoped to teams.
The team slug to perform the request on behalf of. Alternative to teamId for identifying the team.
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://localhost:3000/artifacts/status"{
"status": "disabled"
}{
"code": "string",
"message": "string"
}{
"code": "string",
"message": "string"
}{
"code": "string",
"message": "string"
}