This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
On a security or compliance team? Email info@apievangelist.com with 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 so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
Status: defunct — acquired by IBM (2005). No API surface.
Corio, Inc. was an enterprise Application Service Provider (ASP) founded in September 1998 in San Carlos, California and incorporated in Delaware, formed by acquiring the capital stock of Data Systems Connectors, Inc. Corio implemented, hosted and managed packaged enterprise business software from Oracle, PeopleSoft, SAP, Ariba and Siebel Systems for medium and large public, private, non-profit and public sector customers, delivering ERP, CRM and e-business functionality as a service from secure third-party data centers over IP networks.
The company operated two lines of business — Application Management Services and Professional Services — and partnered with (i)Structure, XO Communications and Qwest for data center and network infrastructure.
Backed by Kleiner Perkins Caufield & Byers (29.5% pre-IPO, held across the KPCB Java Fund, KPCB VIII, KPCB VIII Founders Fund and KPCB Information Sciences Zaibatsu Fund II; Vinod Khosla and Ted Schlein served on the board) and Cap Gemini Ernst & Young. Corio went public on NASDAQ in 2000.
IBM agreed to acquire Corio on 24 January 2005 for $2.82 per share in cash via Nike Acquisition Corp. Corio filed its Form 15 deregistration on 15 March 2005 and was absorbed into IBM.
Identity verified against SEC EDGAR (CIK 0001111001, SIC 7371). The enrichment pipeline found no API, developer portal, documentation, packages, well-known documents, CLI, or event surface:
corio.comresolves to a parked soft-404 catch-all (208.91.197.195) that returns HTTP 200 for every path, including/.well-known/*and/llms.txt— no harvestable well-known artifacts.- No
corioGitHub organization (404). - npm
coriois an empty placeholder with zero published versions; PyPIcoriois unrelated third-party AI/ML tooling byfmtr. Neither is first-party, so no packages artifact was written.