Archade is the professional network for the built world. Structured data is exported from the knowledge graph for research and tools, under clear terms and with attribution requirements. This page explains how to access the dataset APIs, what rate limits apply, how API keys work, and how to use different formats.

---

Base URLs

All dataset APIs follow this pattern:

https://archade.com/api/datasets/{entity}.jsonld

Entities: projects, companies, people, software, institutions, products, jobs, media-intel, relationships, experience, education, company-reviews, entity-reviews, posts

Embeddings: embeddings — requires Commercial or Enterprise API key (returns 401 without)

Example:

https://archade.com/api/datasets/projects.jsonld

---

Query parameters

Examples:

/api/datasets/projects.jsonld?limit=50
/api/datasets/projects.jsonld?limit=50&format=csv
/api/datasets/companies.jsonld?format=json

---

Authentication: API key

For higher limits and rate limits, use an API key.

How to get an API key

1. Log in to Archade
2. Go to Dashboard → Profile → API Keys
3. Click Create API Key
4. Give it a name, choose a tier (Research, Commercial, or Enterprise)
5. Copy the key immediately — you won't see it again

How to use your API key

Option 1: Header (recommended)

X-API-Key: archade_live_abc123...

Option 2: Query parameter

/api/datasets/projects.jsonld?api_key=archade_live_abc123...

Example with curl:

curl -H "X-API-Key: your_key_here" \
  "https://archade.com/api/datasets/projects.jsonld?limit=500"

---

Rate limits

Rate limits depend on whether you use an API key and which tier it has:

Response headers (when available):

• X-RateLimit-Limit — Your limit per minute
• X-RateLimit-Remaining — Requests left in current window
• X-RateLimit-Reset — Unix timestamp when the window resets
• X-RateLimit-Tier — Your current tier
• Retry-After — Seconds to wait (when rate limited)

If you exceed the limit: You'll receive 429 Too Many Requests with a Retry-After header. Slow down and retry after the indicated time.

Per-endpoint tracking: Rate limits are tracked per endpoint, meaning requests to /api/datasets/projects.jsonld and /api/datasets/companies.jsonld are counted separately.

---

Formats

CSV notes:

• Nested objects are flattened (e.g. address.city)
• Arrays are joined with ;
• Filename includes the date (e.g. archade-projects-2026-02-01.csv)

---

Access tiers explained

Research

• Who: Academics, students, non-commercial use
• Limit: 1,000 entities per request, 30 req/min
• How: Create API key, select Research tier
• Cost: Free (contact us for formal research agreements)

Commercial

• Who: Companies building products, tools, or analytics
• Limit: 10,000 entities per request, 100 req/min
• How: Create API key, select Commercial tier
• Cost: Contact legal@archade.app for pricing

Enterprise

• Who: Large-scale use, AI training, custom SLAs
• Limit: 100,000 entities per request, 500 req/min
• How: Contact legal@archade.app for a custom agreement
• Cost: Custom pricing

Note: API keys are per user, not per company. Dataset API access is not included in company subscription tiers (e.g. COMPANY_UNLIMITED). Enterprise agreements may include company-wide keys, dedicated support, and custom terms. Contact us to discuss.

---

CRUD: Read-only

Dataset APIs are read-only. There is no Create, Update, or Delete. You can only read data. To contribute data, use the Archade platform (profiles, projects, companies, etc.). Dataset APIs exist for researchers and downstream consumers, not for data ingestion.

---

Pricing and payment

Payment integration: Commercial and Enterprise tiers are handled via direct agreement. No self-serve checkout for dataset API access. Contact legal@archade.app.

---

Response structure

JSON-LD / JSON:

{
  "@context": "https://schema.org",
  "@type": "Dataset",
  "name": "Archade Projects Dataset",
  "url": "https://archade.com/api/datasets/projects.jsonld",
  "numberOfItems": 50,
  "dateModified": "2026-02-01T...",
  "@graph": [ /* array of Schema.org entities */ ]
}

Each entity in @graph follows Schema.org types (e.g. CreativeWork for projects, Organization for companies).

---

Errors

401 — The Embeddings dataset requires a Commercial or Enterprise API key. Research-tier keys do not grant access.

403 — We block known scraping tools (Scrapy, Selenium, curl, wget, etc.) and requests without a proper User-Agent. For legitimate programmatic use, send a descriptive User-Agent (e.g. MyApp/1.0 (contact@example.com)). Contact help@archade.app if you believe this is in error.

---

Bot detection and User-Agent

We block requests that look like automated scraping. To avoid being blocked:

• Send a descriptive User-Agent — e.g. MyApp/1.0 (research@university.edu) or Archade-Dataset-Client/1.0
• Avoid — Scrapy, Selenium, Puppeteer, curl, wget, or generic/empty User-Agents
• Use an API key when making programmatic requests — keys are associated with your account and help identify legitimate use
• Respect rate limits — Implement proper backoff when receiving 429 responses

If you receive 403, add a proper User-Agent header and retry.

Bot detection patterns: We automatically block requests with user agents matching patterns like Scrapy, Selenium, Puppeteer, curl, wget, headless browsers, or those with Cloudflare bot scores below 30.

---

Best practices

1. Cache responses — Data is stable; avoid repeated identical requests.
2. Use a descriptive User-Agent — Required for programmatic access; see above.
3. Respect rate limits — Implement exponential backoff on 429.
4. Store API keys securely — Never commit them to version control.
5. Rotate keys periodically — Revoke old keys when creating new ones.

---

Related

• Datasets overview — What's in each dataset, contributor vs researcher
• Dataset License — Permitted uses, attribution
• API Keys dashboard — Create and manage keys (requires login)