Preferred Networks
Preferred Networks, Inc. (PFN) is a Tokyo-based AI company founded in March 2014 that vertically integrates the AI value chain from its own MN-Core AI processors and supercomputing infrastructure through to generative-AI foundation models, solutions and products. PFN develops PLaMo, a Japanese large language model built fully from scratch, and offers it commercially through the cloud-hosted PLaMo API — an OpenAI-compatible chat-completions, tokenize and models service at api.platform.preferredai.jp — alongside on-premises, Amazon Bedrock Marketplace, Snowflake and edge (PLaMo Lite) deployment options. PFN also maintains widely used open-source machine-learning software including Optuna, Chainer, PFRL, pytorch-pfn-extras and the PLaMo Translate CLI, which doubles as a locally hosted MCP server.
Preferred Networks publishes 1 API on the APIs.io network. Tagged areas include Company, Artificial Intelligence, Machine-Learning, Large Language Models, and Generative AI.
Preferred Networks’ developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 22 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
PLaMo API
The PLaMo API is Preferred Networks' cloud service for its domestically developed PLaMo large language models. Its interface is compatible with the OpenAI API, so existing OpenA...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Preferred Networks MCP surface
Preferred Networks ships one real MCP server, and it is not for the PLaMo API. The first-party plamo-translate CLI starts an MCP server as part of its `server` command, exposing...
MCP SERVERPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Preferred Networks Rate Limits
RATE LIMITSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.