Skip to main content

Documentation Index

Fetch the complete documentation index at: https://api.superseeded.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Welcome to the SuperSeeded API

The SuperSeeded API provides programmatic access to our services for plant specification parsing, matching, and botanical name verification.

OpenAPI Specification

Download the OpenAPI 3.1.0 specification file

​
Authentication

The SuperSeeded API uses API keys to authenticate requests. You can manage your API keys in the SuperSeeded Dashboard.

​
Obtaining an API key

  1. Log in to your account at superseeded.ai.
  2. Navigate to Settings > API Keys.
  3. Click Create API Key.
  4. Configure your key settings:
    • Name: Give it a descriptive name (e.g., “Production Backend”, “Dev Environment”).
    • Credit limit (optional): Set a maximum usage limit (leave blank for unlimited).
    • Reset frequency: Choose how often the limit resets (e.g., Monthly, Never).
    • Expiration: Set an expiry date if required.
  5. Copy the generated key immediately. You will not be able to see it again.

​
Using your API key

Your API key must be included in the header of every request (excluding the health check endpoint). 
X-API-Key: YOUR_API_KEY
Example request: 
curl -X POST https://api.superseeded.ai/v1/verify/pot-sizes \
  -H "Content-Type: application/json" \
  -H "X-API-Key: sk-sup-v1*****************************************" \
  -d '{
    "items": ["400mm AS", "20L Bag"]
  }'
Or validate botanical names: 
curl -X POST https://api.superseeded.ai/v1/verify/plant-names \
  -H "Content-Type: application/json" \
  -H "X-API-Key: sk-sup-v1*****************************************" \
  -d '{
    "species_names": ["Eucalyptus globulus", "Acacia melanoxylon"]
  }'
Security notice: Do not share your secret API keys in publicly accessible areas such as GitHub or client-side code.

​
Platform Integration (Teams Plan)

If you’re on a Teams plan and building a platform that serves multiple merchants, you can use delegation tokens instead of exposing your API key. This enables per-merchant usage tracking and billing.

Platform Integration Guide

Learn how to authenticate requests on behalf of your merchants