At this stage, the API is used internally by Folding Monitor to support leaderboards, profile pages, team pages, country rankings, search, generated signature cards, and other service features.

A public API is not available yet, but it is part of the long-term product direction.

We use it internally to power the service and to keep the public interface fast, consistent, and reliable.

The internal API helps us work with:

Folding@home user IDs, names, credits, work units, ranks, teams, countries, and activity summaries.

Team IDs, team names, logos, members, credits, work units, rank movement, and leaderboard positions.

Country-based rankings, represented countries, activity summaries, and users without country settings.

24h, 7d, 30d, and all-time rankings for users, teams, and countries.

Forum signature cards, profile previews, and other visual elements based on Folding@home contribution data.

We want a public API to be useful, stable, and responsible.

Opening an API too early can create problems: unstable endpoints, unclear limits, inconsistent data formats, excessive server load, and breaking changes for early users.

Before making public endpoints available, we want to define the important parts properly:

Clear response formats for users, teams, countries, rankings, and time periods.

Reasonable limits that protect the service while still making the API useful.

Transparent expectations around refresh frequency, delays, and historical data.

Clear guidance on how Folding Monitor data should be referenced when used externally.

Endpoints that are reliable enough for developers, community tools, dashboards, and forum integrations.

Careful separation between public statistics, connected-account data, internal service data, and protected technical information.

A future public API may include endpoints for:

Search or retrieve Folding@home user profiles and contribution summaries.

Retrieve team profiles, member counts, logos, rank data, and activity summaries.

Access country-based statistics and rankings across selected time periods.

Fetch top users, teams, and countries for 24h, 7d, 30d, and all-time periods.

Generate or retrieve user and team signature card assets for forums and community pages.

Track leaderboard changes, rising users, active teams, and country participation trends.

Support embeddable widgets for teams, users, forums, and community websites.

If a public API is introduced, it will be designed for responsible use.

The goal is not to create unrestricted scraping or high-volume data extraction. The goal is to support useful community tools, dashboards, forum integrations, team websites, and research-friendly visualizations without harming service stability.

A future API may include:

• API keys;

• rate limits;

• endpoint-specific quotas;

• caching requirements;

• attribution rules;

• abuse prevention;

• versioned endpoints;

• developer documentation.

We are not accepting public API registrations yet.

However, we are interested in hearing what developers, team maintainers, community members, and Folding@home contributors would find useful.

You can send API ideas, endpoint requests, integration needs, or early-access interest to:

general@vitaltale.com

Helpful feedback may include:

• what data you would like to access;

• what kind of project or integration you want to build;

• whether you need user, team, country, or leaderboard data;

• expected request volume;

• preferred data formats;

• whether you need widgets, images, JSON endpoints, or historical statistics.

Public API: not available yet

Internal API: active

Developer documentation: planned

Early access: not open yet

Feedback: welcome at general@vitaltale.com

Folding Monitor is being built with API-readiness in mind, even while the public interface remains the main priority.