Mmeshbase

For e-procurement, marketplaces, fleet operators, and AI agent builders

Stop scraping. Stop stitching. Subscribe to verified data, governed by contract.

One key, many providers, one bill. Pay for what you use — and swap providers without touching your code.

Browse the catalogGet a key

Standards & protocols we work with

  • TecDoc
  • ETIM
  • GS1
  • OCPP
  • MCP
  • OpenAPI
  • GraphQL

What you do today

Five integration patterns that don't scale.

Whether you build for workshops, marketplaces, fleets, or AI agents — the patterns below are the ones we keep replacing.

Pain 1

Scraping breaks every time the provider redesigns

Selectors drift, rate limits change, captchas appear. Every release of theirs is a release of yours. Meanwhile, no governance, no audit, and zero recourse when something breaks.

Pain 2

FTP + CSV doesn't lend itself to real-time

Yesterday's stock data ships today's wrong order. Webhooks were never on offer.

Pain 3

AI agents hallucinate without a clean source

LLMs invent SKUs, mismatch tariffs, and don't carry provenance. Your customers blame your product, not the model.

Pain 4

Per-partner integrations multiply

Each new provider is a custom auth flow, custom mapping, custom rate limit, custom error code, custom invoice. Your code looks like a museum.

Pain 5

Compliance can't answer 'where did this come from?'

Procurement and audit ask for provenance on every record. You can't produce it without rebuilding lineage from sources to outputs. AI Act and DPP make this not optional.

What you get

Four concrete outcomes, no fluff.

Each one maps to a specific bug, ticket, or compliance question you've already had this quarter.

01

Multiple providers, one contract

One Meshbase subscription, multiple providers, one bill. Same auth, same SDK, same error model across all of them. Compare quality, swap providers, scale up — no rewrite.

02

Real-time, not yesterday-time

Streaming subscriptions and webhooks for stock, price, availability, session events. Configure on a per-provider basis through the same client.

03

MCP-ready for your AI agents

Your AI agents call governed MCP tools, not screen-scrapers. Same audit row, same rate limits, same policy as a human user. Your AI compliance becomes data compliance.

04

Provenance on every call

Every response carries lineage: provider, version, freshness, classification. Procurement and AI Act audit answers route through one API.

Quickstart

Five minutes from signup to first governed call.

Same surface as our /developers reference, abridged for first-time use. Sandbox seed data ships with every workspace so you can build before you commit to a provider.

01

SDK

Typed TypeScript client for Node, Next.js, or any modern JS runtime. Best for product engineers who want autocomplete and a single import.

typescript

1. Install

bashbash
npm install @meshbase/sdk

2. Subscribe to a provider, then call

typescripttypescript
import { createClient } from "@meshbase/sdk";

const client = createClient({ apiKey: process.env.MESHBASE_KEY });

// Pick a provider from the catalog, then query
const subscription = await client.useSubscription("YOUR_SUBSCRIPTION_ID");
const { products } = await subscription.catalog.products.list({ first: 10 });
02

REST

Plain HTTP under `/rest/v1`. The lowest-friction option — works from any language, any platform, including legacy ERP/PIM systems.

bash

Use your API key against /rest/v1

bashbash
curl -H "Authorization: Bearer $MESHBASE_KEY" \
-H "x-subscription-id: YOUR_SUBSCRIPTION_ID" \
"https://api.meshbase.ai/rest/v1/products?first=10"
03

MCP

Model Context Protocol — your AI assistant or agent calls Meshbase as a typed tool, under the same caller-governance and audit as a human user.

json

1. Add to your AI tool config

jsonjson
{
"mcpServers": {
  "meshbase": {
    "command": "npx",
    "args": ["-y", "@meshbase/mcp@latest"],
    "env": {
      "MESHBASE_TOKEN": "YOUR_API_KEY",
      "MESHBASE_SUBSCRIPTION_ID": "YOUR_SUBSCRIPTION_ID"
    }
  }
}
}

2. Ask your AI assistant

texttext
"Show me the data products I have access to and what each one returns."

What you can rely on

Pay for access, not for the data. Switch without rewriting.

We are not a data broker. The relationship between you and the provider stays between you. Meshbase delivers the access infrastructure — auth, governance, audit, billing — and stays out of your data.

  • One Meshbase contract spans many providers. Add or remove providers without touching client code.
  • Per-call lineage tells you exactly which provider answered and what version of their data product served it.
  • EU-hosted. GDPR controls implemented today. ISO 27001 and SOC 2 programs in preparation.
  • Tenant export bundles your subscription history, audit trail, and cached data in open JSONL.gz format — anytime.

Subscriber FAQ

What we get asked first.

Five minutes to first call

Browse providers. Pick one. Make a call.

Self-service all the way to your first sandbox response. If you need volume guarantees, custom contracts, or procurement support, talk to us — we'll match you to the right provider plan.