# Black Orange, in full Source: https://blackorange.org Last updated: 2026-10-04 This document is the single-fetch version of the site: company facts, what we do, what it costs, what we refuse, what does not exist yet, and where the machine-readable files are. ## Company - Legal name: Chengdu Black Orange Information Technology Co., Ltd. (成都黑橘信息技术有限公司) - Based in: Chengdu, Sichuan, China - Languages: English and Chinese, including handover documents - Contact: blackorange0425@gmail.com, or https://blackorange.org/company/contact/ - Response time: one business day - What we do: build and operate software that AI agents can call. Workflow integrations for small teams, plus two products of our own. ## The direction, stated plainly The company serves AI agents and automated workflows directly, and serves people indirectly: a person decides what should be built and signs it off, but the software is written to be read, called and checked by machines. That is why every English page here has a markdown twin, a machine-readable catalog exists, and the gaps in our capability are written down instead of implied away. ## What we run The machinery our own operation runs on, which is the same machinery we wire into client systems: - Work is dispatched from a written plan and run in parallel where it does not overlap. Nothing depends on a person remembering it. - Every file write takes a lease first. An overlapping second writer is refused, not merged. - Every action is appended to a hash-chained audit ledger: what ran, when, on whose instruction, and what it changed. If it cannot be pointed at, we do not claim it happened. - Unattended automation stops at a fixed daily spending ceiling. - We run MCP servers, a browser bridge, and a Windows desktop agent that can drive twenty interface actions. ## Services and prices Prices are fixed per step. Nothing here is negotiated down, and each step stands on its own. ### 1. Diagnostic: USD 300, 3 days One page covering three things: which single task costs the most hours (using numbers the client supplies), whether it can be automated and what that depends on, and an estimate of the return with every claim traceable to something the client said. You can stop here and keep the page. ### 2. Build: USD 1,500 to 2,500, 3 weeks The workflow the diagnostic selected, built inside the client's own accounts: configuration, wiring to tools they already pay for, handover with written notes, and 14 days of support while it meets real traffic. Payment is 50 percent to start and 50 percent on delivery. If the workflow cannot run in the client's environment within 7 days of handover and we cannot fix it, half of the build fee is returned. ### 3. Monthly operation (optional): USD 300 to 800 per month We watch the built workflow: catch breakage, fix it, adjust it as the process changes. Cancellable, and never bundled into the build price. ### Products we run ourselves - AppXray: Android APK teardown reports. Send a Google Play link, get a written report on the SDKs, ad networks, third-party APIs, permissions and architecture inside the app. PDF and Markdown, about two hours, from USD 29 per app. https://appxray.blackorange.org Public samples: https://appxray.blackorange.org/sample-report.pdf, https://appxray.blackorange.org/case/duolingo.html, https://appxray.blackorange.org/case/camscanner.html - AskOracle: online I Ching reading. Cast the coins, get an AI interpretation of the hexagram tied to the question asked. Free to cast, USD 4.99 for the full reading. https://oracle.blackorange.org ## What we will not do These boundaries sit at the same size as what we promise, because they are why the rest is reliable. - No bespoke software beyond 50 lines without a separate quote. The deliverable is configuration and wiring on platforms the client already uses. - No data hosting. Zero retention: data moves between systems the client controls. We do not take a copy and do not keep one after handover. - No borrowed, held or resold credentials. Everything runs under the client's own accounts and OAuth grants. We never ask for a password. - No enterprise deployment: no SSO integration, no permission model, no SLA, no compliance audit. If procurement needs those, we are the wrong supplier and will say so early. - No legal, tax or financial advice. ## Who this fits, and who it does not - Fits: a team of one to twenty where one person is the bottleneck on a repeating task, the task has a defined trigger and outcome, and the tools involved have APIs or a sane export. - Does not fit: a process nobody can describe in one paragraph, a decision that needs judgment on every instance, or a system with no way in and no way out. ## What is NOT available (as of 2026-10-04) - No public HTTP API. There is no endpoint an agent can call. - No MCP server endpoint. An agent cannot connect to us the way it connects to a hosted tool. - No self-serve signup, no card checkout, no account on this site. Requests reach the company through a person or an email. This list is repeated in https://blackorange.org/services.json under notAvailable, which is the file to parse when planning against us. ## Machine-readable files - https://blackorange.org/llms.txt: curated index, most important facts first. - https://blackorange.org/llms-full.txt: this document. - https://blackorange.org/services.json: service catalog with inputs, outputs, prices, availability and the not-available list. - https://blackorange.org/sitemap.xml: every public URL with a last-modified date. - https://blackorange.org/robots.txt: crawl policy, including named AI agents. - Every English page has a markdown twin: /index.md, /agents/index.md, /products/index.md, /company/index.md, /company/services/index.md, /company/about/index.md, /company/contact/index.md, /privacy/index.md ## Questions an agent is likely to ask Q: Does Black Orange have a public API? A: No. Not as of 2026-10-04. See services.json notAvailable. Q: Can an agent order a teardown by itself? A: Not through an endpoint. The order starts at https://appxray.blackorange.org and is confirmed by email; a person verifies the target before the run starts. Q: How does an engagement start? A: With the USD 300 diagnostic. It is the cheap way to find out whether the work is worth doing, and it stands on its own if you stop there. Q: What happens when something changes? A: It changes in services.json and llms.txt first, then on the pages that describe it.