Weel

Weel (formerly DiviPay, operated by Weel Pty Ltd) is a Melbourne-based all-in-one spend management platform for finance teams in Australia and New Zealand, serving over 4,000 finance teams and 60,000+ card holders. Weel issues virtual and physical Visa debit cards with real-time limits and controls, and layers accounts payable automation, expense management, reimbursements, subscription management, budgets, and approval policies on top. Rather than operating payment rails directly, Weel sits on the spend and AP/AR seam, syncing approved spend into Xero, QuickBooks, MYOB, and NetSuite. On the API posture, Weel ships a genuine public developer portal at developer.letsweel.com (Redocly-based) documenting a single RESTful "Weel Open API" that both reads and writes budgets, users, transactions, custom fields, accounting codes, categories, invites, and top-ups, authenticated with a bearer API key generated in-app. API access is an Enterprise-tier capability. No public webhooks, Postman collection, or OAuth flow are documented as of this review.

Weel publishes 15 APIs on the APIs.io network, including Accounting Codes API, Budget Members API, Budget Owners API, and 12 more. Tagged areas include Payments, Australia, Spend Management, Expense Management, and Corporate Cards.

Weel’s developer surface includes authentication, documentation, API reference, getting-started guide, pricing, changelog, support, and 19 more developer resources.

🌐 Visit website 📡 Source on GitHub

55.0/100 strong ▬ flat Agent 25/100 agent aware saas Full breakdown ↓
scored 2026-09-06 · rubric v0.19.0

1 APIs

Payments Australia Spend Management Expense Management Corporate Cards Accounts Payable Card Issuing Reimbursement Budgets Fintech

Kin Score

Kin Score How this is scored →
scored 2026-09-06 · rubric v0.19.0

Composite quality — 55.0/100 · strong

Contract Quality 12.2 / 21

Developer Ergonomics 10.0 / 17

Access Clarity 10.3 / 17

Operational Transparency 2.9 / 11

Contract Governance 1.9 / 10

Discoverability 6.5 / 9

Regulatory Posture 8.4 / 15

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 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 5 / 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

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.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

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 github.com/api-evangelist/weel: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 15

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

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgenticAccess

WellKnown

LLMsTxt

AgentSkill

Access & Security 7

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

Authentication

TrustCenter

Compliance

Security

SecurityTxt

Scroll for all 7

Operate 3

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

ChangeLog

ChangeLog

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

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: weel
url: https://raw.githubusercontent.com/api-evangelist/weel/refs/heads/main/apis.yml
name: Weel
kind: company
description: Weel (formerly DiviPay, operated by Weel Pty Ltd) is a Melbourne-based all-in-one spend management platform for
  finance teams in Australia and New Zealand, serving over 4,000 finance teams and 60,000+ card holders. Weel issues virtual
  and physical Visa debit cards with real-time limits and controls, and layers accounts payable automation, expense management,
  reimbursements, subscription management, budgets, and approval policies on top. Rather than operating payment rails directly,
  Weel sits on the spend and AP/AR seam, syncing approved spend into Xero, QuickBooks, MYOB, and NetSuite. On the API posture,
  Weel ships a genuine public developer portal at developer.letsweel.com (Redocly-based) documenting a single RESTful "Weel
  Open API" that both reads and writes budgets, users, transactions, custom fields, accounting codes, categories, invites,
  and top-ups, authenticated with a bearer API key generated in-app. API access is an Enterprise-tier capability. No public
  webhooks, Postman collection, or OAuth flow are documented as of this review.
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-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Payments
- Australia
- Spend Management
- Expense Management
- Corporate Cards
- Accounts Payable
- Card Issuing
- Reimbursement
- Budgets
- Fintech
tags_raw:
- Payments
- Australia
- Spend Management
- Expense Management
- Corporate Cards
- Accounts Payable
- Card Issuing
- Reimbursements
- Budgets
- Fintech
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.23'
apis:
- aid: weel:weel-accounting-codes-api
  name: Weel Accounting Codes API
  description: 'This group of endpoints allows you to manage GL codes (accounting codes) for your business.


    GL codes are used to classify expenses for bookkeeping export. Businesses with a connected accounting integration (Xero,
    MYOB, NetSuite, QuickBooks, Business Central) cannot create or delete GL codes via the API — those are managed by the
    integration sync. Businesses with a manual integration or no integration can freely create, update, and delete GL codes.
    A manual integration is automatically created on the first POST if none exists.'
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Accounting Codes
  properties:
  - type: OpenAPI
    url: openapi/weel-accounting-codes-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-budget-members-api
  name: Weel Budget Members API
  description: This group of endpoints allows you to retrieve and manage budget member data, including listing budget members
    and fetching individual budget member details.
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Budget Members
  properties:
  - type: OpenAPI
    url: openapi/weel-budget-members-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-budget-owners-api
  name: Weel Budget Owners API
  description: 'This group of endpoints allows you to retrieve and manage budget owners. A budget owner is a user (or pending
    invite) who can approve spend, top up, and otherwise manage the budget.


    A budget must always have at least one active owner — deleting the last remaining owner is not permitted. Adding an owner
    who was previously removed will reinstate the original record rather than create a duplicate.'
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Budget Owners
  properties:
  - type: OpenAPI
    url: openapi/weel-budget-owners-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-budget-topups-api
  name: Weel Budget Topups API
  description: "This group of endpoints allows you to retrieve and create budget topups. Topups are used to increase or decrease\
    \ the available amount of a budget or budget member.\n\nTopups will be automatically approved, unless a Workflow or Policy\
    \ has been configured in Weel for that requires approval for budget topups.\n\nThere are two types of topups:\n  - Budget\
    \ topups are used to increase or decrease the available amount of a budget. This is only\npermitted when `has_member_limits`\
    \ is `false` for the budget.\n  - Budget member topups are used to increase or decrease the available amount of a budget\
    \ member.\nThis is only permitted when `has_member_limits` is `true` for the budget.\n`has_member_limits` is set to `true`\
    \ when this toggle is enabled in the budget creation form.\n  ![Has Member Limits is true](assets/has-member-limits-true.png)"
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Budget Topups
  properties:
  - type: OpenAPI
    url: openapi/weel-budget-topups-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-budgets-api
  name: Weel Budgets API
  description: 'This group of endpoints allows you to retrieve and manage budget data, including listing budgets and fetching
    individual budget details.


    Budgets are organised in a hierarchy where a budget can have multiple members. Each member is associated with a user.
    Funds can be allocated at the budget level or at the member level, using the flag `has_member_limits`.


    ![Budget Hierachy](assets/budget-hierarchy.png)'
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Budgets
  properties:
  - type: OpenAPI
    url: openapi/weel-budgets-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-categories-api
  name: Weel Categories API
  description: 'This group of endpoints allow you to manage expense categories for your business.


    Categories classify transactions. System-defined categories (`custom: false`) can only have their `enabled` state toggled.
    Custom categories (`custom: true`) can have their `name` updated and can be deleted.'
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Categories
  properties:
  - type: OpenAPI
    url: openapi/weel-categories-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-custom-field-budgets-api
  name: Weel Custom Field Budgets API
  description: This group of endpoints allows you to link custom fields to budgets, controlling which budgets have a custom
    field assigned.
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Custom Field Budgets
  properties:
  - type: OpenAPI
    url: openapi/weel-custom-field-budgets-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-custom-field-options-api
  name: Weel Custom Field Options API
  description: This group of endpoints allows you to manage the list options for a `LIST` type custom field. Options created
    via the Public API can be disabled or deleted.
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Custom Field Options
  properties:
  - type: OpenAPI
    url: openapi/weel-custom-field-options-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-custom-fields-api
  name: Weel Custom Fields API
  description: 'This group of endpoints allows you to create and manage custom fields (dimensions/cost centres) for your business.


    Custom fields can be of type `LIST` (with predefined options) or `FREE_TEXT`. Custom fields created via the Public API
    have a `created_by` value of `PUBLIC_API`.


    Custom fields created by accounting integrations (Xero, MYOB, QuickBooks, NetSuite, Business Central) have restrictions:
    their name and type cannot be modified via the Public API.'
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Custom Fields
  properties:
  - type: OpenAPI
    url: openapi/weel-custom-fields-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-invites-api
  name: Weel Invites API
  description: This group of endpoints allows you to create, list, and cancel pending user invitations. An invite exists until
    the recipient accepts it, at which point they appear as a user in the Users endpoints.
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Invites
  properties:
  - type: OpenAPI
    url: openapi/weel-invites-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-roles-api
  name: Weel Roles API
  description: This group of endpoints allows you to retrieve the roles available within a business and the permissions assigned
    to each role.
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Roles
  properties:
  - type: OpenAPI
    url: openapi/weel-roles-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-statements-api
  name: Weel Statements API
  description: This group of endpoints allows you to retrieve a list of balances for the required period for a given business.
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Statements
  properties:
  - type: OpenAPI
    url: openapi/weel-statements-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-tax-rates-api
  name: Weel Tax Rates API
  description: 'This group of endpoints allows you to retrieve the tax rates configured for your business. Tax rates are read-only
    via the Public API.


    For businesses with a connected accounting integration (Xero, MYOB, NetSuite, QuickBooks, Business Central), the tax rates
    synced from that integration are returned. Businesses without a connected integration get their own manually configured
    tax rates.'
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Tax Rates
  properties:
  - type: OpenAPI
    url: openapi/weel-tax-rates-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-transactions-api
  name: Weel Transactions API
  description: This group of endpoints allows you to retrieve and manage transaction data, including listing transactions
    with various filters and fetching individual transaction details.
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/weel-transactions-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
- aid: weel:weel-users-api
  name: Weel Users API
  description: This group of endpoints allows you to retrieve and manage user data, including listing users and fetching individual
    user details.
  humanURL: https://developer.letsweel.com/openapi
  baseURL: https://public.letsweel.com
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/weel-users-api-openapi.yml
  - type: Documentation
    url: https://developer.letsweel.com/
  - type: APIReference
    url: https://developer.letsweel.com/openapi
  - type: Authentication
    url: https://developer.letsweel.com/getting-started/authentication
  - type: GettingStarted
    url: https://developer.letsweel.com/getting-started/authentication
  - type: ToolCrosswalk
    url: mcp/weel-tool-crosswalk.yml
  - type: ErrorCatalog
    url: errors/weel-problem-types.yml
  - type: DataModel
    url: data-model/weel-data-model.yml
  - type: Conventions
    url: conventions/weel-conventions.yml
  - type: Lifecycle
    url: lifecycle/weel-lifecycle.yml
  - type: Conformance
    url: conformance/weel-conformance.yml
common:
- type: X-MCPServerCandidate
  url: mcp/weel-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: Overlay
  url: overlays/weel-openapi-overlay.yaml
- type: AgenticAccess
  url: agentic-access/weel-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/weel-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/weel-domain-security.yml
- type: Authentication
  url: authentication/weel-authentication.yml
- type: Website
  url: https://letsweel.com/
- type: DeveloperPortal
  url: https://developer.letsweel.com/
- type: Documentation
  url: https://developer.letsweel.com/
- type: APIReference
  url: https://developer.letsweel.com/openapi
- type: GettingStarted
  url: https://developer.letsweel.com/getting-started/authentication
- type: Pricing
  url: https://letsweel.com/pricing
- type: ChangeLog
  url: https://letsweel.com/product-updates
- type: TrustCenter
  url: https://trust.letsweel.com/
- type: Compliance
  url: security/weel-trust-center.yml
- type: Security
  url: security/weel-vulnerability-disclosure.yml
- type: WellKnown
  url: well-known/weel-well-known.yml
- type: SecurityTxt
  url: well-known/weel-security.txt
- type: LLMsTxt
  url: llms/weel-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: ChangeLog
  url: changelog/weel-changelog.yml
- type: Support
  url: https://help.letsweel.com/hc/en-us
- type: Blog
  url: https://letsweel.com/resources/the-weelhouse
- type: TermsOfService
  url: https://letsweel.com/terms
- type: PrivacyPolicy
  url: https://letsweel.com/privacy
- type: SignUp
  url: https://app.letsweel.com/app/business-signup
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/weel"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/weel/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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