Fudo

Fudo is a cloud-based point-of-sale and restaurant management platform used by more than 25,000 restaurants, bars, and cafes across Latin America. The product covers on-premise and online sales, QR menus, kitchen display, inventory and purchasing, expenses, table and room management, staff roles, and delivery-app integrations (Uber Eats, Rappi, PedidosYa). Fudo publishes a general-purpose public REST API (OpenAPI 3.1, JSON:API style) that lets Pro-plan accounts read and write sales, payments, products, customers, expenses, ingredients, and system configuration for reporting, BI, ERP, and custom integrations. This profile was surfaced as an a16z portfolio company and enriched by the API Evangelist pipeline from Fudo's own developer surface.

Fudo publishes 19 API contracts indexed on the APIs.io network, including Customers API, Discounts API, Expense Categories API, and 16 more. Tagged areas include Company, Restaurant, Point-of-Sale, Hospitality, and Food and Beverage.

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

Fudo’s developer surface includes authentication, documentation, API reference, support, engineering blog, pricing, signup flow, and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

41.0/100 developing ▬ flat Agent 26/100 agent aware Front door AI 2/6 trace Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract

Company Restaurant Point-of-Sale Hospitality Food and Beverage Payments Inventory Latin America Software-as-a-Service

What this lets a business do 1

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

Pricing Management

BC-440

Discounts

POST /discounts PATCH /discounts/{id}

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 41.0/100 · developing

Contract Quality 10.4 / 19

Developer Ergonomics 6.8 / 15

Access Clarity 6.7 / 15

Operational Transparency 0.0 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments 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.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/fudo/"><img src="https://apis.io/badge/fudo/card.svg" alt="Fudo 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Operational Transparency scores 0.0 — up to +13.0 composite points
Contract Quality scores 55.3 — up to +11.2 composite points
Access Clarity scores 44.7 — up to +11.1 composite points

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/fudo/apis.yml: open an issue on github.com/api-evangelist/fudo 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.

Market	Position	Depth	Registered MCP server	Declares compatibility
Argentine Fintech Registers (BCRA PSP + entities, CNV agents + PSAV, Cámara Fintech)	standard	51.7	-	-
Browser Extension Stores (company-published Firefox add-ons; Chrome Web Store unreadable)	standard	51.7	-	-

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 1

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 19

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

Fudo Customers API

The Customers API from Fudo — 2 operation(s) for customers.

Fudo Discounts API

The Discounts API from Fudo — 2 operation(s) for discounts.

Fudo Expense Categories API

The Expense Categories API from Fudo — 2 operation(s) for expense categories.

Fudo Expenses API

The Expenses API from Fudo — 2 operation(s) for expenses.

Fudo Ingredients API

The Ingredients API from Fudo — 2 operation(s) for ingredients.

Fudo Items API

The Items API from Fudo — 2 operation(s) for items.

Fudo Kitchens API

The Kitchens API from Fudo — 2 operation(s) for kitchens.

Fudo Payment Methods API

The Payment Methods API from Fudo — 2 operation(s) for payment methods.

Fudo Payments API

The Payments API from Fudo — 2 operation(s) for payments.

Fudo Product Categories API

The Product Categories API from Fudo — 2 operation(s) for product categories.

Fudo Product Modifiers API

The Product Modifiers API from Fudo — 2 operation(s) for product modifiers.

Fudo Products API

The Products API from Fudo — 2 operation(s) for products.

Fudo Providers API

The Providers API from Fudo — 2 operation(s) for providers.

Fudo Roles API

The Roles API from Fudo — 2 operation(s) for roles.

Fudo Rooms API

The Rooms API from Fudo — 2 operation(s) for rooms.

Fudo Sales API

The Sales API from Fudo — 2 operation(s) for sales.

Fudo Subitems API

The Subitems API from Fudo — 1 operation(s) for subitems.

Fudo Tables API

The Tables API from Fudo — 2 operation(s) for tables.

Fudo Users API

The Users API from Fudo — 2 operation(s) for users.

Scroll for all 19

Open Collections 19

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

Fudo Customers API

OPEN COLLECTION

Fudo Customers Discounts API

OPEN COLLECTION

Fudo Customers Expense Categories API

OPEN COLLECTION

Fudo Customers Expenses API

OPEN COLLECTION

Fudo Customers Ingredients API

OPEN COLLECTION

Fudo Customers Items API

OPEN COLLECTION

Fudo Customers Kitchens API

OPEN COLLECTION

Fudo Customers Payment Methods API

OPEN COLLECTION

Fudo Customers Payments API

OPEN COLLECTION

Fudo Customers Product Categories API

OPEN COLLECTION

Fudo Customers Product Modifiers API

OPEN COLLECTION

Fudo Customers Products API

OPEN COLLECTION

Fudo Customers Providers API

OPEN COLLECTION

Fudo Customers Roles API

OPEN COLLECTION

Fudo Customers Rooms API

OPEN COLLECTION

Fudo Customers Sales API

OPEN COLLECTION

Fudo Customers Subitems API

OPEN COLLECTION

Fudo Customers Tables API

OPEN COLLECTION

Fudo Customers Users API

OPEN COLLECTION

Scroll for all 19

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Fudo API Rules

49 rules · 47 errors 1 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.

Fudo Openapi Overlay

3 actions · update · fudo-openapi-original.yml

DERIVED

Security Posture 2

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

Fudo Authentication

http · 1 scheme

SECURITY

Fudo Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: fudo
name: Fudo
description: Fudo is a cloud-based point-of-sale and restaurant management platform used by more than 25,000 restaurants,
  bars, and cafes across Latin America. The product covers on-premise and online sales, QR menus, kitchen display, inventory
  and purchasing, expenses, table and room management, staff roles, and delivery-app integrations (Uber Eats, Rappi, PedidosYa).
  Fudo publishes a general-purpose public REST API (OpenAPI 3.1, JSON:API style) that lets Pro-plan accounts read and write
  sales, payments, products, customers, expenses, ingredients, and system configuration for reporting, BI, ERP, and custom
  integrations. This profile was surfaced as an a16z portfolio company and enriched by the API Evangelist pipeline from Fudo's
  own developer surface.
url: https://raw.githubusercontent.com/api-evangelist/fudo/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
x-tier: profiled
x-tier-reason: portfolio-lead
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: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
image: https://dev.fu.do/assets/images/fudo.svg
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Restaurant
- Point-of-Sale
- Hospitality
- Food and Beverage
- Payments
- Inventory
- Latin America
- Software-as-a-Service
tags_raw:
- Company
- Restaurant
- Point of Sale
- Hospitality
- Food and Beverage
- Payments
- Inventory
- Latin America
- SaaS
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: fudo:fudo-customers-api
  name: Fudo Customers API
  description: The Customers API from Fudo — 2 operation(s) for customers.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Customers
  properties:
  - type: OpenAPI
    url: openapi/fudo-customers-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-discounts-api
  name: Fudo Discounts API
  description: The Discounts API from Fudo — 2 operation(s) for discounts.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Discounts
  properties:
  - type: OpenAPI
    url: openapi/fudo-discounts-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-expense-categories-api
  name: Fudo Expense Categories API
  description: The Expense Categories API from Fudo — 2 operation(s) for expense categories.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Expense Categories
  properties:
  - type: OpenAPI
    url: openapi/fudo-expense-categories-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-expenses-api
  name: Fudo Expenses API
  description: The Expenses API from Fudo — 2 operation(s) for expenses.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Expenses
  properties:
  - type: OpenAPI
    url: openapi/fudo-expenses-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-ingredients-api
  name: Fudo Ingredients API
  description: The Ingredients API from Fudo — 2 operation(s) for ingredients.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Ingredients
  properties:
  - type: OpenAPI
    url: openapi/fudo-ingredients-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-items-api
  name: Fudo Items API
  description: The Items API from Fudo — 2 operation(s) for items.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Item
  tags_raw:
  - Items
  properties:
  - type: OpenAPI
    url: openapi/fudo-items-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-kitchens-api
  name: Fudo Kitchens API
  description: The Kitchens API from Fudo — 2 operation(s) for kitchens.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Kitchens
  properties:
  - type: OpenAPI
    url: openapi/fudo-kitchens-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-payment-methods-api
  name: Fudo Payment Methods API
  description: The Payment Methods API from Fudo — 2 operation(s) for payment methods.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Payment Methods
  properties:
  - type: OpenAPI
    url: openapi/fudo-payment-methods-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-payments-api
  name: Fudo Payments API
  description: The Payments API from Fudo — 2 operation(s) for payments.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/fudo-payments-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-product-categories-api
  name: Fudo Product Categories API
  description: The Product Categories API from Fudo — 2 operation(s) for product categories.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Product Categories
  properties:
  - type: OpenAPI
    url: openapi/fudo-product-categories-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-product-modifiers-api
  name: Fudo Product Modifiers API
  description: The Product Modifiers API from Fudo — 2 operation(s) for product modifiers.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Product Modifiers
  properties:
  - type: OpenAPI
    url: openapi/fudo-product-modifiers-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-products-api
  name: Fudo Products API
  description: The Products API from Fudo — 2 operation(s) for products.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Product
  tags_raw:
  - Products
  properties:
  - type: OpenAPI
    url: openapi/fudo-products-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-providers-api
  name: Fudo Providers API
  description: The Providers API from Fudo — 2 operation(s) for providers.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Providers
  properties:
  - type: OpenAPI
    url: openapi/fudo-providers-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-roles-api
  name: Fudo Roles API
  description: The Roles API from Fudo — 2 operation(s) for roles.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Roles
  properties:
  - type: OpenAPI
    url: openapi/fudo-roles-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-rooms-api
  name: Fudo Rooms API
  description: The Rooms API from Fudo — 2 operation(s) for rooms.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Rooms
  properties:
  - type: OpenAPI
    url: openapi/fudo-rooms-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-sales-api
  name: Fudo Sales API
  description: The Sales API from Fudo — 2 operation(s) for sales.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Sales
  properties:
  - type: OpenAPI
    url: openapi/fudo-sales-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-subitems-api
  name: Fudo Subitems API
  description: The Subitems API from Fudo — 1 operation(s) for subitems.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Subitems
  properties:
  - type: OpenAPI
    url: openapi/fudo-subitems-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-tables-api
  name: Fudo Tables API
  description: The Tables API from Fudo — 2 operation(s) for tables.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - Tables
  properties:
  - type: OpenAPI
    url: openapi/fudo-tables-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
- aid: fudo:fudo-users-api
  name: Fudo Users API
  description: The Users API from Fudo — 2 operation(s) for users.
  humanURL: https://dev.fu.do/api/
  baseURL: https://api.fu.do/v1alpha1
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/fudo-users-api-openapi.yml
  - type: APIReference
    url: https://dev.fu.do/api/
common:
- type: CapabilityMap
  url: capabilities/fudo-capability-edges.yml
  name: Fudo Business Capability Map
- type: DomainSecurity
  url: security/fudo-domain-security.yml
- type: Authentication
  url: authentication/fudo-authentication.yml
- type: X-MCPServerCandidate
  url: mcp/fudo-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/fudo-llms.txt
- type: Overlay
  url: overlays/fudo-openapi-overlay.yaml
- type: Conformance
  url: conformance/fudo-conformance.yml
- type: ErrorCatalog
  url: errors/fudo-problem-types.yml
- type: Lifecycle
  url: lifecycle/fudo-lifecycle.yml
- type: Conventions
  url: conventions/fudo-conventions.yml
- type: DataModel
  url: data-model/fudo-data-model.yml
- type: DeveloperPortal
  url: https://dev.fu.do/api/
- type: Documentation
  url: https://dev.fu.do/api/
- type: APIReference
  url: https://dev.fu.do/api/
- type: Support
  url: https://soporte.fu.do
- type: Blog
  url: https://blog.fu.do/
- type: Pricing
  url: https://fu.do/es/precios/
- type: SignUp
  url: https://fu.do/es/crear-cuenta/
- type: Login
  url: https://app-v2.fu.do/
- type: TermsOfService
  url: https://fu.do/condiciones-de-servicio/
- type: PrivacyPolicy
  url: https://fu.do/es/politicas-de-privacidad/
- type: Website
  url: https://fu.do
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Fudo API — frequently asked questions

Does Fudo have an API?

Yes. APIs.io lists 19 APIs from Fudo, including Fudo Customers API, Fudo Discounts API and Fudo Expense Categories API, and 16 more.

Is there an OpenAPI specification for the Fudo API?

Yes. APIs.io indexes 19 OpenAPI specifications for Fudo, each linked for download from this page.

How do I authenticate with the Fudo API?

Fudo uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Fudo Authentication.

Is the Fudo API ready for AI agents?

Fudo has a Kin Score of 41.0 out of 100 (developing) and an Agent Readiness score of 25.5 (agent-aware), 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/fudo"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/fudo/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/fudo/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.

GitHub Google LinkedIn

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