Forithmus
Forithmus builds foundation models for medical imaging (Zurich, Switzerland; pre-seed backed by Point Nine and e2vc). Its developer-facing product is the Forithmus Research Hub, a Challenge Platform where research teams host and enter medical-imaging benchmarks by submitting Docker containers or prediction files, with leaderboards, credits and compute tiers, collections, forums, and groups. The public REST API is served at https://research.forithmus.com/api and described by an OpenAPI 3.1.0 specification (172 paths, 213 operations across 24 tags: auth/2FA, challenges, phases, collections, submissions, leaderboard, credits, payments, forum, groups, and more). Authentication is Bearer JWT via email/password or Google OAuth, with a browser device flow used by the first-party `forithmus` CLI. Forithmus also publishes open model/dataset repositories (MR-RATE, VLM3D, FORA) on GitHub.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Forithmus the way a machine reads it — 29 machine-readable artifacts across 25 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Forithmus scores 38.5/100 (thin), with a separate agent-readiness read of 64/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Forithmus
Each block below is one kind of artifact we hold for Forithmus. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 25
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Forithmus 2fa API
The 2fa API from Forithmus — 5 operation(s) for 2fa.
Forithmus admin API
The admin API from Forithmus — 15 operation(s) for admin.
Forithmus auth API
The auth API from Forithmus — 13 operation(s) for auth.
Forithmus challenges API
The challenges API from Forithmus — 7 operation(s) for challenges.
Forithmus collections API
The collections API from Forithmus — 15 operation(s) for collections.
Forithmus credits API
The credits API from Forithmus — 16 operation(s) for credits.
Forithmus data-upload API
The data-upload API from Forithmus — 8 operation(s) for data-upload.
Forithmus forum API
The forum API from Forithmus — 7 operation(s) for forum.
Forithmus groups API
The groups API from Forithmus — 10 operation(s) for groups.
Forithmus Health API
The Health API from Forithmus — 2 operation(s) for health.
Forithmus images API
The images API from Forithmus — 1 operation(s) for images.
Forithmus leaderboard API
The leaderboard API from Forithmus — 2 operation(s) for leaderboard.
Forithmus members API
The members API from Forithmus — 7 operation(s) for members.
Forithmus messages API
The messages API from Forithmus — 5 operation(s) for messages.
Forithmus notifications API
The notifications API from Forithmus — 3 operation(s) for notifications.
Forithmus pages API
The pages API from Forithmus — 3 operation(s) for pages.
Forithmus payments API
The payments API from Forithmus — 6 operation(s) for payments.
Forithmus phases API
The phases API from Forithmus — 6 operation(s) for phases.
Forithmus resources API
The resources API from Forithmus — 5 operation(s) for resources.
Forithmus roles API
The roles API from Forithmus — 6 operation(s) for roles.
Forithmus search API
The search API from Forithmus — 1 operation(s) for search.
Forithmus submissions API
The submissions API from Forithmus — 18 operation(s) for submissions.
Forithmus timeline API
The timeline API from Forithmus — 2 operation(s) for timeline.
Forithmus uploads API
The uploads API from Forithmus — 1 operation(s) for uploads.
Forithmus users API
The users API from Forithmus — 8 operation(s) for users.
Scroll within the panel for all 25 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
forithmus-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Forithmus — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/forithmus · machine-readable index on apis.io