Skip to content
OmniscapeRenders API
All pages
  1. Overview
  2. Quick start
  3. Authentication
  4. API reference
    1. GET /media
    2. POST /media
    3. GET /media/{id}/preview
    4. GET /integrations/google/connect
    5. GET /integrations/google
    6. DELETE /integrations/google
    7. GET /integrations/google/folders
    8. POST /media/import
    9. GET /media/imports/{id}
    10. POST /renders
    11. GET /renders/{id}
    12. GET /renders/{id}/download
    13. GET /usage
  5. Code examples
  6. Error handling
  7. Rate limits & quotas
  8. Troubleshooting
  9. Changelog

Reference

GET

/api/v1/usage

Requires the renders:read scope.

This billing cycle's render counts. Counts only — never dollars, cost, or provider detail.

Request

curl -s "https://omniscape.io/api/v1/usage" \
  -H "Authorization: Bearer $OMNISCAPE_API_KEY"

Response

{
  "object": "usage",
  "cycle_start": "2026-08-04T01:17:11.000Z",
  "aesthetic_quotes": { "used": 16, "included": null }
}

Notes

  • included: null means the plan’s allowance is unlimited.
  • This reports the account allowance for the billing cycle. It is a different number from your key’s daily spend cap, which is per key and rolls off over 24 hours — see Rate limits & quotas.

Codes this call can return are on Error handling. If something is behaving unexpectedly, Troubleshooting is organised by symptom.