Discover/Cosmos API
live

Cosmos APIcosmos.so

Search the Cosmos curated database via API. Find images, videos, links, notes, and products by keyword, color, or content type. Browse collections with pagination.

Endpoint health
verified 2d ago
search_elements
search_collections
2/2 passing latest checkself-healing
Endpoints
2
Updated
26d ago

What is the Cosmos API?

The Cosmos.so API provides 2 endpoints for searching a curated database of visual and multimedia elements. search_elements returns up to 40 results per page across images, videos, links, notes, and products — each with media URLs, captions, source attribution, and owner details. search_collections retrieves curated groups of elements with follower counts, element counts, and cover images, supporting page sizes up to 100.

Try it
Filter results by color (hex color code without # prefix, e.g. 'FF0000' for red). Omitted returns all colors.
Sort order for results. Omitted defaults to relevance sorting.
Search term to find elements (e.g. 'architecture', 'nature', 'minimalist design').
Pagination cursor from a previous response's next_page_cursor field. Omitted returns the first page.
Filter by content type. Omitted returns all content types.
api.parse.bot/scraper/518f0113-a227-49a8-95cf-31124444fa1e/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X POST 'https://api.parse.bot/scraper/518f0113-a227-49a8-95cf-31124444fa1e/search_elements' \
  -H 'X-API-Key: $PARSE_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "order": "RELEVANT",
  "query": "architecture",
  "content_type": "IMAGE"
}'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace cosmos-so-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""
Cosmos Image Search API - Parse SDK Example
Search for curated visual content and collections on Cosmos.
"""

from parse_apis.cosmos_image_search_api import Cosmos, ContentType, ElementOrder, CollectionSort

cosmos = Cosmos()

# Search for architecture images sorted by popularity
for element in cosmos.elements.search(query="architecture", content_type=ContentType.IMAGE, order=ElementOrder.POPULAR, limit=5):
    print(element.id, element.caption, element.share_url)

# Search for collections about typography sorted by size
for collection in cosmos.collections.search(query="typography", sort=CollectionSort.LARGEST, limit=3):
    print(collection.name, collection.number_of_elements, collection.followers_count)
All endpoints · 2 totalmissing one? ·

Full-text search over Cosmos elements (images, videos, links, notes, products). Matches query against captions and metadata. Returns up to 40 results per page. Each element includes media URLs, captions, source attribution, and owner details. Paginate via the next_page_cursor returned in each response. Color filtering accepts a hex code; content_type and order restrict or reorder results server-side.

Input
ParamTypeDescription
colorstringFilter results by color (hex color code without # prefix, e.g. 'FF0000' for red). Omitted returns all colors.
orderstringSort order for results. Omitted defaults to relevance sorting.
queryrequiredstringSearch term to find elements (e.g. 'architecture', 'nature', 'minimalist design').
page_cursorstringPagination cursor from a previous response's next_page_cursor field. Omitted returns the first page.
content_typestringFilter by content type. Omitted returns all content types.
Response
{
  "type": "object",
  "fields": {
    "items": "array of element objects with id, type, created_at, share_url, owner, caption, source, media, and type-specific fields",
    "total_count": "integer total number of matching results",
    "next_page_cursor": "string cursor for fetching the next page, null if no more pages"
  },
  "sample": {
    "data": {
      "items": [
        {
          "id": 2019059012,
          "type": "MediaElementTile",
          "media": {
            "url": "https://cdn.cosmos.so/c39f5bbd-3155-44f8-aadf-2ce88422d7c3",
            "width": 1200,
            "height": 1600,
            "mediaId": "c39f5bbd-3155-44f8-aadf-2ce88422d7c3",
            "blurHash": "00PjAI",
            "__typename": "StaticImage",
            "aiGenerated": false,
            "notSafeForWorkStatus": "SAFE"
          },
          "owner": {
            "username": "papillon",
            "__typename": "UserPublicProfile",
            "verifiedProfile": null,
            "isVerifiedProfile": false
          },
          "source": {
            "url": "https://baukobox.de/projekte/366",
            "author": null,
            "__typename": "ElementSource",
            "isEditable": false,
            "isPublicDomain": false
          },
          "caption": "The facade of the Bestseller Office Complex in Aarhus.",
          "share_url": "https://www.cosmos.so/e/2019059012",
          "created_at": "2024-09-27T16:02:40.934003Z",
          "is_featured": false,
          "multiple_media": []
        }
      ],
      "total_count": 500,
      "next_page_cursor": "cursor://api_gateway/element_search?query=architecture&last=39&count=500"
    },
    "status": "success"
  }
}

About the Cosmos API

What the API Returns

The search_elements endpoint accepts a required query string and matches it against captions and metadata across all Cosmos element types. Each result object includes an id, type, created_at timestamp, share_url, owner details, caption, source attribution, and media URLs. Optional parameters let you narrow results: content_type filters to a specific element kind (image, video, link, note, or product), color accepts a hex code without the # prefix (e.g. FF0000) to filter by dominant color, and order controls sort direction. Pagination is cursor-based — the response includes a next_page_cursor string that you pass as page_cursor on the next request, or null when there are no further pages. The total_count field tells you how many total records matched.

Searching Collections

The search_collections endpoint searches Cosmos's curated collections — thematic groupings of elements maintained by users. Results include id, name, slug, cover image, owner, number_of_elements, and followers_count. You can control page size with page_size (1–100) and sort results using the sort parameter: POPULAR orders by followers descending, LARGEST orders by element count descending, and omitting sort defaults to relevance. Pagination works the same way as elements — pass next_page_cursor back as page_cursor on subsequent calls.

Coverage and Scope

Both endpoints cover publicly accessible Cosmos content. Element searches return type-specific fields alongside the common fields, so a product result may carry different metadata than an image result. Color filtering on search_elements is specific to visually dominant color and only applies when a hex value is provided; omitting the parameter returns results across all colors.

Reliability & maintenanceVerified

The Cosmos API is a managed, monitored endpoint for cosmos.so — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when cosmos.so changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official cosmos.so API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
2d ago
Latest check
2/2 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build a mood board tool that queries search_elements by keyword and color hex to surface visually matching images.
  • Aggregate curated design collections by sorting search_collections results by POPULAR to surface trending topics.
  • Create a design research feed that paginates through search_elements results for a niche query like 'brutalist typography'.
  • Power an internal asset discovery tool that filters search_elements by content_type to return only videos or products.
  • Index Cosmos collections for a creative directory by extracting name, slug, number_of_elements, and followers_count.
  • Identify top contributors by extracting owner details from high-follower collections returned by search_collections.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min

One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Cosmos.so have an official developer API?+
Cosmos.so does not publish a documented public developer API. The Parse API provides structured access to Cosmos element and collection data without requiring any account or credentials.
What does the `search_elements` endpoint return for each result?+
Each element object includes id, type, created_at, share_url, owner (with user details), caption, source (attribution metadata), and media (URLs for the associated file or embed). Type-specific fields may also be present depending on whether the element is an image, video, link, note, or product.
How does pagination work across both endpoints?+
Both endpoints use cursor-based pagination. Each response includes a next_page_cursor string. Pass that value as page_cursor in your next request to retrieve the following page. When next_page_cursor is null, you have reached the last page. The total_count field in each response reports the full number of matching results.
Can I retrieve the individual elements inside a specific collection?+
Not currently. The search_collections endpoint returns collection metadata — cover image, owner, element count, and follower count — but does not return the list of elements contained within a collection. You can fork this API on Parse and revise it to add an endpoint that fetches a collection's element contents by collection ID or slug.
Is color filtering available when searching collections?+
Color filtering via the color parameter is only available on search_elements, not on search_collections. Collection searches support keyword queries and sorting by popularity or size. You can fork this API on Parse and revise it to add color-based filtering to the collections search if that capability becomes relevant to your use case.
Page content last updated . Spec covers 2 endpoints from cosmos.so.
Related APIs in OtherSee all →
cos.com API
Search and browse COS fashion products by name or category to instantly access pricing, product images, and direct links to items. Retrieve detailed information about specific products including descriptions, availability, and pricing to compare styles and make informed shopping decisions.
opensea.io API
Search NFT collections and discover detailed stats, browse individual items, and track collection activity all in one place. Get real-time insights into collection performance and find the NFTs you're looking for on OpenSea.
pexels.com API
Search and browse millions of free stock photos and videos on Pexels. Access trending content, photographer galleries, photo/video challenges, and search suggestions via a clean API.
elements.envato.com API
Search and browse millions of creative assets from Envato Elements, including stock photos, videos, music, fonts, and templates across all categories. Get detailed information about specific items, pricing plans, and discover new content through keyword search and category browsing.
coloso.global API
Discover and browse Coloso's entire course catalog by searching products, filtering by categories, and viewing details on new releases, best sellers, and free classes. Get insights into promotional events, trending keywords, and personalized recommendations to find the perfect creative courses.
images.nasa.gov API
images.nasa.gov API
blenderkit.com API
Search BlenderKit's extensive library of 3D models, materials, scenes, HDRs, and brushes, complete with detailed asset information and category browsing. Retrieve intelligent search suggestions and explore organized collections to discover assets across any creative domain.
textures.com API
Search and browse millions of textures by category or keyword to find high-resolution texture maps with detailed pricing and specifications. Discover the latest content additions, explore free samples, and access complete metadata including available resolutions and texture maps for your projects.