Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature] Add FPT AI Factory as a provider

Open
#4,041 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript
Domain
ai

Research direction

Review implementation #3735 and the proposed providers/fpt-ai-factory/ files first. Verify the provider.toml, square logo.svg, and eight model entries against the public GET /v1/models catalog, including costs, limits, and the empty reasoning_options setting; done means the provider is represented accurately and uses FPT_API_KEY.

Written by the indexing model from the issue text.

Description

Provider

FPT AI Factory — OpenAI-compatible gateway at https://mkp-api.fptcloud.com/v1, serving LLM/VLM models on NVIDIA GB300 nodes.

Why

FPT AI Factory is a first-party Vietnamese cloud AI marketplace not yet in models.dev. It exposes a public catalog endpoint (GET /v1/models) with pricing and limits, making it straightforward to keep in sync.

Scope

Add providers/fpt-ai-factory/ with provider.toml, a square logo.svg, and 8 model entries (DeepSeek-V4-Flash, Qwen3.6-27B, GLM-5.2, gpt-oss-120b/20b, gemma-4-26B/31B, Llama-3.3-70B). Costs/limits sourced from the live catalog; reasoning_options = [] (gateway exposes no reasoning control).

Implementation

Implemented in #3735.

Env

FPT_API_KEY — keys at https://marketplace.fptcloud.com/ · docs https://ai-docs.fptcloud.com/

Dominant language
TypeScript
Stars
7.2k
Forks
1.8k
Avg merge
1h 12m
Merged PRs (30d)
911

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anomalyco/models.dev

All issues in anomalyco/models.dev

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.