Weld website screenshot

Weld

Weld is a programmable data-infrastructure platform for moving and transforming data. It runs near real-time ELT/ETL pipelines from 300+ prebuilt connectors, log-based Change Data Capture (CDC), SQL-based data transformations with lineage and version history, and Reverse ETL to activate modeled data back into operational tools. The Weld Connect REST API and a hosted Model Context Protocol (MCP) server let developers and AI agents create connections, run and monitor ELT syncs, build and publish transforms, and orchestrate pipelines programmatically. Weld is a Copenhagen-based company backed by a16z and other leading investors.

Weld publishes 13 API contracts indexed on the APIs.io network, including Connection Bridge API, Connections API, Custom Reports API, and 10 more. Tagged areas include Company, Data, ETL, ELT, and Reverse ETL.

The Weld catalog on APIs.io includes 1 Spectral governance ruleset.

Weld’s developer surface includes authentication, documentation, API reference, getting-started guide, engineering blog, pricing, support, and 23 more developer resources.

54.9/100 strong ▬ flat Agent 54/100 agent ready Front door AI 6/6 dominant Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessPaid
1 published contract 1 MCP Servers 3 Agent Skills
CompanyDataETLELTReverse ETLData PipelineData IntegrationChange Data CaptureTransformationAnalyticsMCPAI Agents

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Information & Data Management
BC-610
ELT Syncs
GET /elt_syncs POST /elt_syncs GET /elt_syncs/{id} GET /elt_syncs/{id}/available_source_streams

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Weld It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/weld/"><img src="https://apis.io/badge/weld/card.svg" alt="Weld on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
  • Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
  • Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's
  • Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter
2 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/weld/apis.yml: open an issue on github.com/api-evangelist/weld to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

MarketPositionDepthRegistered MCP serverDeclares compatibility
Commerce Platform Ecosystems (Shopify, WooCommerce, Stripe Apps) builds-on 17.2 (thin) - -

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 4

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (verified)
measured — observed by APIs.io (verified)
measured — observed by APIs.io (published)
measured — observed by APIs.io (published)

APIs 13

Individual APIs this provider publishes, each with its own machine-readable definition.

Weld Connection Bridge API

The Connection Bridge API from Weld — 1 operation(s) for connection bridge.

Weld Connections API

The Connections API from Weld — 3 operation(s) for connections.

Weld Custom Reports API

The Custom Reports API from Weld — 1 operation(s) for custom reports.

Weld ELT Stream Runs API

The ELT Stream Runs API from Weld — 2 operation(s) for elt stream runs.

Weld ELT Streams API

The ELT Streams API from Weld — 5 operation(s) for elt streams.

Weld ELT Syncs API

The ELT Syncs API from Weld — 8 operation(s) for elt syncs.

Weld Integrations API

The Integrations API from Weld — 1 operation(s) for integrations.

Weld Orchestration Runs API

The Orchestration Runs API from Weld — 2 operation(s) for orchestration runs.

Weld Orchestrations API

The Orchestrations API from Weld — 3 operation(s) for orchestrations.

Weld Reverse ETL Failed Records API

The Reverse ETL Failed Records API from Weld — 4 operation(s) for reverse etl failed records.

Weld Reverse ETL Sync Runs API

The Reverse ETL Sync Runs API from Weld — 2 operation(s) for reverse etl sync runs.

Weld Reverse ETL Syncs API

The Reverse ETL Syncs API from Weld — 9 operation(s) for reverse etl syncs.

Weld Transforms API

The Transforms API from Weld — 11 operation(s) for transforms.

Scroll for all 13

Open Collections 13

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll for all 13

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Weld MCP Server

Official hosted Weld MCP server. Lets AI assistants (Claude Desktop, claude.ai, Claude Code, Cursor, GitHub Copilot, Windsurf, and other MCP clients) interact directly with a We...

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Weld API pricing

Prices published by Weld, read 2026-10-28 from weld.app/pricing.

PlanPrice
Basic $99 per month, billed yearly
Includes: 2 connectors, 1 user, Daily syncs, 1 destination, 5M Monthly Active Rows
Premium $389 per month, billed yearly
Includes: 6 connectors, 3 users, Hourly syncs, 1 destination, 10M Monthly Active Rows
Business $959 per month, billed yearly
Includes: 10 connectors, 5 users, 15-minute syncs, Multiple destinations, 50M Monthly Active Rows
Enterprise Talk to us
Includes: Custom connector limit, custom users, 5-minute syncs, CDC

Plan details, limits and sources →

Billed by: subscription · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Weld Plans Pricing

4 plans

PLANS

Weld Price Estimates

0 plans

PLANS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Weld

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Weld Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Weld API Rules

54 rules · 44 errors 9 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Weld Connect Overlay

3 actions · update · weld-connect-openapi.json

DERIVED

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Weld Authentication

apiKey · 1 scheme

SECURITY

Weld Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Weld Trust Center

SOC 2, ISO 27001, GDPR

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Weld Agentic Access

65 operations · 32 acting · 32 human-in-the-loop

65 operations · 32 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Access & Security 4

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: weld
name: Weld
description: Weld is a programmable data-infrastructure platform for moving and transforming data. It runs near real-time
  ELT/ETL pipelines from 300+ prebuilt connectors, log-based Change Data Capture (CDC), SQL-based data transformations with
  lineage and version history, and Reverse ETL to activate modeled data back into operational tools. The Weld Connect REST
  API and a hosted Model Context Protocol (MCP) server let developers and AI agents create connections, run and monitor ELT
  syncs, build and publish transforms, and orchestrate pipelines programmatically. Weld is a Copenhagen-based company backed
  by a16z and other leading investors.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://weld.app/opengraph-image.png
url: https://raw.githubusercontent.com/api-evangelist/weld/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
x-tier: profiled
x-tier-reason: enriched-from-portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Data
- ETL
- ELT
- Reverse ETL
- Data Pipeline
- Data Integration
- Change Data Capture
- Transformation
- Analytics
- MCP
- AI Agents
tags_raw:
- Company
- Data
- ETL
- ELT
- Reverse ETL
- Data Pipelines
- Data Integration
- Change Data Capture
- Transformations
- Analytics
- MCP
- AI Agents
apis:
- aid: weld:weld-connection-bridge-api
  name: Weld Connection Bridge API
  description: The Connection Bridge API from Weld — 1 operation(s) for connection bridge.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - Connection Bridge
  properties:
  - type: OpenAPI
    url: openapi/weld-connection-bridge-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-connections-api
  name: Weld Connections API
  description: The Connections API from Weld — 3 operation(s) for connections.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - Connections
  properties:
  - type: OpenAPI
    url: openapi/weld-connections-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-custom-reports-api
  name: Weld Custom Reports API
  description: The Custom Reports API from Weld — 1 operation(s) for custom reports.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - Custom Reports
  properties:
  - type: OpenAPI
    url: openapi/weld-custom-reports-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-elt-stream-runs-api
  name: Weld ELT Stream Runs API
  description: The ELT Stream Runs API from Weld — 2 operation(s) for elt stream runs.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - ELT Stream Runs
  properties:
  - type: OpenAPI
    url: openapi/weld-elt-stream-runs-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-elt-streams-api
  name: Weld ELT Streams API
  description: The ELT Streams API from Weld — 5 operation(s) for elt streams.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - ELT Streams
  properties:
  - type: OpenAPI
    url: openapi/weld-elt-streams-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-elt-syncs-api
  name: Weld ELT Syncs API
  description: The ELT Syncs API from Weld — 8 operation(s) for elt syncs.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - ELT Syncs
  properties:
  - type: OpenAPI
    url: openapi/weld-elt-syncs-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-integrations-api
  name: Weld Integrations API
  description: The Integrations API from Weld — 1 operation(s) for integrations.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - Integration
  tags_raw:
  - Integrations
  properties:
  - type: OpenAPI
    url: openapi/weld-integrations-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-orchestration-runs-api
  name: Weld Orchestration Runs API
  description: The Orchestration Runs API from Weld — 2 operation(s) for orchestration runs.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - Orchestration Runs
  properties:
  - type: OpenAPI
    url: openapi/weld-orchestration-runs-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-orchestrations-api
  name: Weld Orchestrations API
  description: The Orchestrations API from Weld — 3 operation(s) for orchestrations.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - Orchestration
  tags_raw:
  - Orchestrations
  properties:
  - type: OpenAPI
    url: openapi/weld-orchestrations-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-reverse-etl-failed-records-api
  name: Weld Reverse ETL Failed Records API
  description: The Reverse ETL Failed Records API from Weld — 4 operation(s) for reverse etl failed records.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - Reverse ETL Failed Records
  properties:
  - type: OpenAPI
    url: openapi/weld-reverse-etl-failed-records-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-reverse-etl-sync-runs-api
  name: Weld Reverse ETL Sync Runs API
  description: The Reverse ETL Sync Runs API from Weld — 2 operation(s) for reverse etl sync runs.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - Reverse ETL Sync Runs
  properties:
  - type: OpenAPI
    url: openapi/weld-reverse-etl-sync-runs-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-reverse-etl-syncs-api
  name: Weld Reverse ETL Syncs API
  description: The Reverse ETL Syncs API from Weld — 9 operation(s) for reverse etl syncs.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - Reverse ETL Syncs
  properties:
  - type: OpenAPI
    url: openapi/weld-reverse-etl-syncs-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
- aid: weld:weld-transforms-api
  name: Weld Transforms API
  description: The Transforms API from Weld — 11 operation(s) for transforms.
  humanURL: https://weld.app/docs/api-reference
  baseURL: https://connect.weld.app
  tags:
  - Transforms
  properties:
  - type: OpenAPI
    url: openapi/weld-transforms-api-openapi.yml
  - type: Documentation
    url: https://weld.app/docs/api-reference
  - type: GettingStarted
    url: https://weld.app/docs/weld-connect/getting-started
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/weld-plans-pricing.yml
- type: CapabilityMap
  url: capabilities/weld-capability-edges.yml
  name: Weld Business Capability Map
- type: TrustCenter
  url: security/weld-trust-center.yml
- type: DomainSecurity
  url: security/weld-domain-security.yml
- type: AgenticAccess
  url: agentic-access/weld-agentic-access.yml
- type: Authentication
  url: authentication/weld-authentication.yml
- type: MCPServer
  url: mcp/weld-mcp.yml
- type: Conventions
  url: conventions/weld-conventions.yml
- type: ErrorCatalog
  url: errors/weld-problem-types.yml
- type: Lifecycle
  url: lifecycle/weld-lifecycle.yml
- type: Conformance
  url: conformance/weld-conformance.yml
- type: Compliance
  url: https://weld.app/security
- type: DataModel
  url: data-model/weld-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Overlay
  url: overlays/weld-connect-overlay.yaml
- type: LLMsTxt
  url: llms/weld-llms.txt
- type: WellKnown
  url: well-known/weld-well-known.yml
- type: SLA
  url: https://weld.app/service-level-agreement
- type: DeveloperPortal
  url: https://weld.app/docs
- type: Documentation
  url: https://weld.app/docs
- type: APIReference
  url: https://weld.app/docs/api-reference
- type: GettingStarted
  url: https://weld.app/docs/weld-connect/getting-started
- type: Blog
  url: https://weld.app/blog
- type: Pricing
  url: https://weld.app/pricing
- type: Support
  url: https://weld.app/support
- type: SignUp
  url: https://workspace.weld.app/signup
- type: TermsOfService
  url: https://weld.app/terms-of-service
- type: PrivacyPolicy
  url: https://weld.app/privacy-policy
- type: StatusPage
  url: https://status.weld.app/
- type: Website
  url: https://weld.app
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 18
  pass: local-v1

Weld API — frequently asked questions

Does Weld have an API?

Yes. APIs.io lists 13 APIs from Weld, including Weld Connection Bridge API, Weld Connections API and Weld Custom Reports API, and 10 more.

Is there an OpenAPI specification for the Weld API?

Yes. APIs.io indexes 13 OpenAPI specifications for Weld, each linked for download from this page.

How do I authenticate with the Weld API?

Weld documents its authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Weld Authentication.

How much does the Weld API cost?

Weld publishes its prices; its Basic plan is $99 per month, billed yearly as of 2026-10-28. APIs.io lists 4 pricing plans for Weld, with each plan's price, limits and inclusions under Pricing on this page.

Does Weld have an MCP server?

Yes. APIs.io lists 1 MCP server for Weld: Official hosted Weld MCP server. Lets AI assistants (Claude Desktop, claude.ai, Claude Code, Cursor, GitHub Copilot, Windsurf, and other MCP clients) interact directly with a Weld workspace — listing

Is the Weld API ready for AI agents?

Weld has a Kin Score of 54.9 out of 100 (strong) and an Agent Readiness score of 53.8 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/weld"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/weld/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/weld/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.