1<!doctype html> 2<html lang="en"> 3<head> 4 <meta charset="utf-8"> 5 <meta name="viewport" content="width=device-width, initial-scale=1"> 6 <title>About HolySheep AI â API interfaces, model access, and CLI</title> 7 <meta name="description" content="A factual overview of HolySheep AI: public API base URL, OpenAI-compatible Responses and Chat Completions, Anthropic-compatible Messages, model discovery, CLI platforms, and support contact."> 8 <meta name="robots" content="index,follow,max-image-preview:large,max-snippet:-1,max-video-preview:-1"> 9 <meta name="author" content="HolySheep AI"> 10 <meta name="date" content="2026-07-22"> 11 <link rel="canonical" href="https://www.holysheep.ai/about/"> 12 <link rel="alternate" type="text/plain" href="https://www.holysheep.ai/llms.txt" title="HolySheep AI summary for language models"> 13 <link rel="alternate" type="application/rss+xml" href="https://www.holysheep.ai/feed.xml" title="HolySheep AI documentation updates"> 14 <meta property="og:type" content="article"> 15 <meta property="og:title" content="About HolySheep AI"> 16 <meta property="og:description" content="Service scope, API interfaces, model discovery, CLI platforms, and canonical documentation links."> 17 <meta property="og:url" content="https://www.holysheep.ai/about/"> 18 <meta property="og:site_name" content="HolySheep AI"> 19 <meta name="twitter:card" content="summary"> 20
20<script type="application/ld+json"> 21 { 22 "@context": "https://schema.org", 23 "@graph": [ 24 { 25 "@type": "Organization", 26 "@id": "https://www.holysheep.ai/#organization", 27 "name": "HolySheep AI", 28 "url": "https://www.holysheep.ai/", 29 "email": "[email protected]" 30 }, 31 { 32 "@type": "WebPage", 33 "@id": "https://www.holysheep.ai/about/#webpage", 34 "url": "https://www.holysheep.ai/about/", 35 "name": "About HolySheep AI", 36 "description": "A factual overview of HolySheep AI service scope, documented API interfaces, model discovery, CLI support, and contact information.", 37 "dateModified": "2026-07-22", 38 "isPartOf": { 39 "@id": "https://www.holysheep.ai/#website" 40 }, 41 "about": { 42 "@id": "https://www.holysheep.ai/about/#service" 43 }, 44 "inLanguage": ["en", "zh-CN"] 45 }, 46 { 47 "@type": "WebSite", 48 "@id": "https://www.holysheep.ai/#website", 49 "name": "HolySheep AI", 50 "url": "https://www.holysheep.ai/", 51 "publisher": { 52 "@id": "https://www.holysheep.ai/#organization" 53 } 54 }, 55 { 56 "@type": "Service", 57 "@id": "https://www.holysheep.ai/about/#service", 58 "name": "HolySheep AI API access", 59 "serviceType": "Multi-model AI API access and developer-tool configuration", 60 "url": "https://www.holysheep.ai/about/", 61 "provider": { 62 "@id": "https://www.holysheep.ai/#organization" 63 }, 64 "description": "A unified access layer for models currently listed by HolySheep AI, with documented OpenAI-compatible and Anthropic-compatible interfaces and a cross-platform setup CLI." 65 }, 66 { 67 "@type": "TechArticle", 68 "@id": "https://www.holysheep.ai/about/#technical-overview", 69 "url": "https://www.holysheep.ai/about/", 70 "mainEntityOfPage": { 71 "@id": "https://www.holysheep.ai/about/#webpage" 72 }, 73 "headline": "Technical overview: API interfaces, model access, and CLI", 74 "description": "A factual technical overview of HolySheep AI service scope, API interfaces, live model discovery, CLI platforms, and verification boundaries.", 75 "inLanguage": ["en", "zh-CN"], 76 "datePublished": "2026-07-18T15:00:00+08:00", 77 "dateModified": "2026-07-22T12:30:00+08:00", 78 "author": { 79 "@id": "https://www.holysheep.ai/#organization" 80 }, 81 "publisher": { 82 "@id": "https://www.holysheep.ai/#organization" 83 } 84 }, 85 { 86 "@type": "FAQPage", 87 "@id": "https://www.holysheep.ai/about/#faq", 88 "mainEntity": [ 89 { 90 "@type": "Question", 91 "name": "Which API formats does HolySheep AI document?", 92 "acceptedAnswer": { 93 "@type": "Answer", 94 "text": "HolySheep AI documents OpenAI-compatible Responses and Chat Completions endpoints and an Anthropic-compatible Messages endpoint." 95 } 96 }, 97 { 98 "@type": "Question", 99 "name": "Is HolySheep AI an official OpenAI or Anthropic service?", 100 "acceptedAnswer": { 101 "@type": "Answer", 102 "text": "No official-provider relationship is claimed. HolySheep AI is an independent access and compatibility service." 103 } 104 }, 105 { 106 "@type": "Question", 107 "name": "Where can developers check current model availability?", 108 "acceptedAnswer": { 109 "@type": "Answer", 110 "text": "Use the live model catalog at https://www.holysheep.ai/model because model inventories can change." 111 } 112 } 113 ] 114 } 115 ] 116 } 117 </script>
117 118 <style> 119 :root { 120 color-scheme: light; 121 --ink: #172033; 122 --muted: #536176; 123 --line: #d9e0e9; 124 --surface: #ffffff; 125 --soft: #f4f7fb; 126 --accent: #2457d6; 127 --accent-dark: #183f9e; 128 --code: #101828; 129 } 130 * { box-sizing: border-box; } 131 body { 132 margin: 0; 133 color: var(--ink); 134 background: var(--soft); 135 font: 16px/1.7 system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; 136 } 137 a { color: var(--accent-dark); text-underline-offset: 0.18em; } 138 a:hover { color: var(--accent); } 139 header, main, footer { width: min(960px, calc(100% - 32px)); margin-inline: auto; } 140 header { padding: 24px 0 12px; } 141 nav { display: flex; flex-wrap: wrap; gap: 10px 18px; align-items: center; } 142 nav a:first-child { font-weight: 750; text-decoration: none; color: var(--ink); margin-right: auto; } 143 main { background: var(--surface); border: 1px solid var(--line); border-radius: 18px; padding: clamp(24px, 5vw, 56px); box-shadow: 0 14px 38px rgba(18, 34, 66, 0.07); } 144 h1 { font-size: clamp(2rem, 5vw, 3.4rem); line-height: 1.1; letter-spacing: -0.035em; margin: 0 0 18px; } 145 h2 { font-size: clamp(1.35rem, 3vw, 1.8rem); line-height: 1.25; margin: 44px 0 12px; } 146 h3 { margin: 24px 0 6px; } 147 p, li { max-width: 76ch; } 148 .lead { color: var(--muted); font-size: 1.18rem; } 149 .notice { border-left: 4px solid var(--accent); background: #eef4ff; padding: 14px 18px; border-radius: 0 10px 10px 0; } 150 .grid { display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 14px; margin: 22px 0; } 151 .card { border: 1px solid var(--line); border-radius: 12px; padding: 18px; background: #fff; } 152 .card h3 { margin-top: 0; } 153 code { font-family: ui-monospace, SFMono-Regular, Consolas, monospace; background: #eef1f5; padding: 0.12em 0.35em; border-radius: 4px; overflow-wrap: anywhere; } 154 pre { background: var(--code); color: #f7f9fc; padding: 18px; border-radius: 10px; overflow-x: auto; line-height: 1.55; } 155 pre code { padding: 0; background: transparent; } 156 dt { font-weight: 750; margin-top: 18px; } 157 dd { margin: 5px 0 0; color: var(--muted); max-width: 76ch; } 158 footer { color: var(--muted); padding: 24px 0 42px; font-size: 0.92rem; } 159 @media (max-width: 720px) { .grid { grid-template-columns: 1fr; } nav a:first-child { width: 100%; } } 160 </style> 161</head> 162<body> 163 <header> 164 <nav aria-label="Primary navigation"> 165 <a href="https://www.holysheep.ai/">HolySheep AI</a> 166 <a href="https://www.holysheep.cn/tutorial">Tutorial</a> 167 <a href="https://www.holysheep.ai/model">Models</a> 168 <a href="https://www.holysheep.ai/pricing">Pricing</a> 169 <a href="https://www.holysheep.ai/download">Download</a> 170 </nav> 171 </header> 172 173 <main> 174 <article> 175 <h1>About HolySheep AI</h1> 176 <p class="lead">HolySheep AI is an independent multi-model API access service. It provides a public API base, documented compatibility interfaces, a live model catalog, and setup guidance for developer tools.</p> 177 178 <p class="notice"><strong>Service boundary:</strong> HolySheep AI does not claim to be OpenAI, Anthropic, or another model provider, and does not claim an official-provider relationship. Compatibility describes the request and response formats supported by HolySheep routes. Provider and product names belong to their respective owners.</p> 179 180 <h2>What the service does</h2> 181 <p>A registered user can create a HolySheep API key and use it with the models currently available to that account. One key can cover models listed in the <a href="https://www.holysheep.ai/model">live model catalog</a>, reducing the need to maintain a separate credential in every supported tool. Model availability changes over time, so integrations should copy identifiers from the live catalog instead of relying on a static list or guessing an identifier from a display name.</p> 182 <p>The public API base is <code>https://api.holysheep.cn</code>. HolySheep publishes direct request examples and SDK configuration guidance in the <a href="https://www.holysheep.cn/tutorial">
182Tutorial</a>. Current account-facing price information is maintained on the <a href="https://www.holysheep.ai/pricing">Pricing page</a>. Those live pages take precedence over cached summaries, search snippets, and third-party descriptions.</p> 183 184 <div class="grid" aria-label="Documented API interfaces"> 185 <section class="card"> 186 <h3>Responses</h3> 187 <p>OpenAI-compatible requests at <code>/v1/responses</code> for clients designed around the Responses contract.</p> 188 </section> 189 <section class="card"> 190 <h3>Chat Completions</h3> 191 <p>OpenAI-compatible requests at <code>/v1/chat/completions</code> for applications using a messages-and-choices contract.</p> 192 </section> 193 <section class="card"> 194 <h3>Messages</h3> 195 <p>Anthropic-compatible requests at <code>/v1/messages</code> for applications using Anthropic-style content blocks.</p> 196 </section> 197 </div> 198 199 <p>These interfaces are distinct contracts. Applications should choose the interface expected by their SDK and response parser. Support for ordinary text generation does not imply support for every provider-specific beta field, built-in tool, streaming event, or advanced option. Test required capabilities against the selected HolySheep route and exact model before production use.</p> 200 201 <h2>Reference request shape</h2> 202 <p>This minimal Chat Completions example uses a placeholder rather than a real credential or model. Select the current model identifier on the model page and store the key in a secret manager or environment variable.</p> 203 <pre><code>curl https://api.holysheep.cn/v1/chat/completions \ 204 -H "Authorization: Bearer YOUR_HOLYSHEEP_KEY" \ 205 -H "Content-Type: application/json" \ 206 -d '{ 207 "model": "MODEL_ID_FROM_CATALOG", 208 "messages": [{"role": "user", "content": "Hello"}] 209 }'</code></pre> 210 <p>For OpenAI-style SDKs, the base URL is commonly <code>https://api.holysheep.cn/v1</code>. For an Anthropic-style SDK, use the HolySheep base documented in the tutorial so that the SDK constructs the versioned Messages path correctly. Raw HTTP clients should use the complete endpoint URL.</p> 211 212 <h2>CLI and supported operating systems</h2> 213 <p>HolySheep CLI is documented for Windows, macOS, and Linux. It helps configure supported AI developer tools and provides diagnostic workflows. See the current <a href="https://www.holysheep.cn/tutorial">installation and configuration guide</a> and the public <a href="https://www.npmjs.com/package/@simonyea/holysheep-cli" rel="external noreferrer">@simonyea/holysheep-cli npm package</a>. A public source repository is not linked in these discovery assets.</p> 214 <p>Before an automated setup, back up any tool configuration that has been customized manually. After setup, make a short request and verify the final endpoint, selected model, response contract, and account usage. Do not commit generated configuration until confirming that it contains no API key. Cross-platform CLI support does not mean that every third-party tool supports automatic setup on every platform; consult the current tutorial for each tool's status.</p> 215 216 <h2>Authentication and account facts</h2> 217 <p>Keys are created through the <a href="https://www.holysheep.ai/register">registration and account flow</a>. The current public registration material describes a promotional <strong>$0.5 registration credit</strong>. This is a current promotion rather than a permanent guarantee; confirm the registration page when signing up. How much work a credit funds depends on the selected model, token usage, media usage where applicable, and current prices.</p> 218 <p>Keep API keys in an operating-system credential store, environment variable, or deployment secret manager. Never place a private key in browser JavaScript, a public repository, an issue, an analytics event, a screenshot, or an email. If a credential is exposed, revoke or replace it. Removing one visible copy does not reliably remove it from logs, repository history, or backups.</p> 219 220 <h2>Integration principles</h2> 221 <ul> 222 <li>Use the live model catalog as the source for current identifiers and availability.</li> 223 <li>Use the live pricing page for current prices and record the retrieval date in published comparisons.<
223/li> 224 <li>Keep endpoint, interface, and model selection explicit in application configuration.</li> 225 <li>Apply bounded retries only to transient failures; do not retry invalid requests or unsupported features unchanged.</li> 226 <li>Set timeouts appropriate to streaming and non-streaming work, and support cancellation.</li> 227 <li>Log sanitized error metadata, never authorization headers or secrets.</li> 228 <li>Validate application-side tool actions and structured output before using them for business decisions.</li> 229 </ul> 230 231 <h2>Primary technical references</h2> 232 <p>Provider documentation is useful for understanding upstream concepts. The relevant primary references are the <a href="https://platform.openai.com/docs/api-reference/responses" rel="external noreferrer">OpenAI Responses API reference</a>, <a href="https://platform.openai.com/docs/api-reference/chat" rel="external noreferrer">OpenAI Chat API reference</a>, and <a href="https://docs.anthropic.com/en/api/messages" rel="external noreferrer">Anthropic Messages API reference</a>. Use HolySheep documentation to determine HolySheep-specific compatibility and routing. Provider documentation alone is not evidence that every provider feature is available through a compatibility service.</p> 233 234 <h2 id="faq">Frequently asked questions</h2> 235 <dl> 236 <dt>Can one HolySheep key call more than one model?</dt> 237 <dd>Yes. One key can call models currently available to the account and shown in the HolySheep catalog. This is not a promise that every model is permanently available.</dd> 238 239 <dt>Which interface should an application choose?</dt> 240 <dd>Choose the contract the client and parser expect: Responses, Chat Completions, or Messages. Keep separate adapters if the application uses more than one.</dd> 241 242 <dt>Are model prices stored on this page?</dt> 243 <dd>No. Prices are time-sensitive. Check the live pricing page and record the date when creating a cost estimate or comparison.</dd> 244 245 <dt>Does compatibility include every built-in provider tool?</dt> 246 <dd>No universal claim is made. Test the exact tool, model, and route. Treat an unsupported-feature response as a compatibility boundary, not as a successful execution.</dd> 247 248 <dt>Where are machine-readable facts published?</dt> 249 <dd>Start with <a href="https://www.holysheep.ai/llms.txt">llms.txt</a>, the <a href="https://www.holysheep.ai/llms-full.txt">full guide</a>, and the <a href="https://www.holysheep.ai/.well-known/ai.txt">AI discovery file</a>. Structured JSON resources are linked from those documents.</dd> 250 251 <dt>How can I contact HolySheep AI?</dt> 252 <dd>Email <a href="mailto:[email protected]">[email protected]</a>. Include the endpoint, model identifier, timestamp, and sanitized error, but never include an API key.</dd> 253 </dl> 254 255 <h2>ä¸ææè¦</h2> 256 <p>HolySheep AI æ¯ç¬ç«çå¤æ¨¡å API æ¥å ¥ä¸å ¼å®¹æå¡ãå ¬å¼ API åºç¡å°å为 <code>https://api.holysheep.cn</code>ï¼ææ¡£è¦ç OpenAI å ¼å®¹ç ResponsesãChat Completions æ¥å£ï¼ä»¥å Anthropic å ¼å®¹ç Messages æ¥å£ãä¸ä¸ª HolySheep å¯é¥å¯è°ç¨è´¦æ·å½åå¯ç¨ä¸å¨å®æ¶æ¨¡åç®å½ä¸å±ç¤ºç模åï¼ä½è¿ä¸è¡¨ç¤ºææ模åæ°¸ä¹ å¯ç¨ã</p> 257 <p>模åä¸ä»·æ ¼å±äºå¨æä¿¡æ¯ï¼è¯·åå«æ¥ç<a href="https://www.holysheep.ai/model">å®æ¶æ¨¡åç®å½</a>å<a href="https://www.holysheep.ai/pricing">å®æ¶ä»·æ ¼é¡µ</a>ãCLI ææ¡£è¦ç WindowsãmacOS ä¸ LinuxãHolySheep AI ä¸å£°ç§°ä¸ OpenAIãAnthropic æå ¶ä»æ¨¡ååååå¨å®æ¹å ³ç³»ï¼å ¼å®¹æ§æè¿°åªä»£è¡¨ HolySheep è·¯ç±ææ¯æçæ¥å£è¡ä¸ºã</p> 258 259 <h2>Contact and document status</h2> 260 <p>Email <a href="mailto:[email protected]">[email protected]</a> for product, documentation, account, or security questions. Do not send a credential. This page was reviewed on <time datetime="2026-07-22">22 July 2026</time>. Models, prices, promotions, packages, and compatibility details can change, so consult the linked live pages before making a time-sensitive decision.</p> 261 </article> 262 </main> 263 264 <footer> 265 <p>© 2026 HolySheep AI · <a href="https://www.holysheep.ai/llms.txt">llms.txt</a> · <a href="https://www.holysheep.ai/sitemap-core.xml">Sitemap</a> · <a href="mailto:[email protected]">[email protected]</a></p> 266 </footer> 267</body> 268</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.