Aipingji
Aipingji (爱拼机, also romanized Apin / Aipinji) was a Hangzhou, China travel-technology startup — legal entity 杭州爱拼机网络科技有限公司, incorporated 7 May 2015 in the Binjiang district — that built a C2B "intelligent group-buying" marketplace for discounted international air tickets. Rather than reselling published fares, it aggregated the unsold seat inventory of roughly a thousand Chinese charter operators (包机商), who buy blocks of seats from airlines in advance, and let consumers form 10-15 person buying groups against a specific date until the group filled and tickets were issued, taking a reported 5% commission from the charter operator. The app served 36 destinations from Hangzhou, Shanghai and Nanjing, and the company raised an angel round (Aug 2015, 天使汇), a tens-of-millions-RMB Series A (Apr 2016, led by 耀途资本 with 光合基金 and others), a ¥120M Series B (Jan 2017, 华映资本 and 弘帆资本) and a Series B+ (Jun 2017, 一村资本, 华映资本, Century Capital, Shenxuan Investment). No first-party surface survives: the domain cited as its site, apin.com, is now a parked listing offered for sale at ¥199,999 through the Chinese domain broker ename.com.cn and answers 403 on every path but the sale lander, the mobile app's last recorded update was September 2017, and there is no developer portal, GitHub organization, published package, or API of any kind.
Aipingji is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
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. The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Aipingji's operating domain apin.com is now a for-sale parking page at the Chinese domain broker ename.com.cn — the root returns the "您正在访问的域名可以转让 / This domain is for sale" lander and every deeper path, including /openapi.json, /llms.txt, /robots.txt and /.well-known/agent-card.json, returns 403 — so STEP 0b contract discovery had no live first-party host to run against; aipingji.com, aipinji.com and api.aipingji.com do not resolve, there is no GitHub organization or published npm/PyPI package under any spelling of the name, and the company's app has no recorded update since September 2017.
This is an honest zero, not a gap in our research. Aipingji does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
http://apin.com/→ HTTP 200https://apin.com/→ HTTP 0http://apin.com/openapi.json→ HTTP 403http://apin.com/llms.txt→ HTTP 403http://apin.com/.well-known/agent-card.json→ HTTP 403http://apin.com/.well-known/security.txt→ HTTP 403https://aipingji.com/→ HTTP 0https://api.aipingji.com/→ HTTP 0http://www.belephtro.com/→ HTTP 0https://api.github.com/orgs/aipingji→ HTTP 404https://registry.npmjs.org/aipingji→ HTTP 404https://pypi.org/pypi/aipingji/json→ HTTP 404https://www.linkedin.com/company/aipingji/→ HTTP 404https://equityzen.com/company/aipingji/→ HTTP 200https://www.cbinsights.com/company/aipinji→ HTTP 200
Resources
Every other property we hold for Aipingji — 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.
Other 1
Properties that don't map to a standard resource type
Aipingji is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/aipingji · machine-readable index on apis.io
This is an independent, third-party profile of Aipingji, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.