KEYXE Open Source
We believe useful examples, documented interfaces, and carefully reviewed developer tools can help more people understand and build technology.
KEYXE follows a selective open-source approach. We intend to share original, publication-safe components while keeping customer information, access credentials, and privately operated SaaS infrastructure protected. Each release will clearly state its scope, license, and actual status.
Why we share
Developers learn from working examples. Students learn from transparent explanations. Communities strengthen technology when a project invites feedback and makes its interfaces understandable. Our aim is to contribute resources that others can inspect, adapt and improve — without releasing data that belongs to customers.
Working examples teach faster than descriptions.
Tool schemas, synthetic datasets and metric functions show exactly how an analytics workflow is put together — what goes in, what comes out, and where the limits are. The free guides in the Learning Center explain the ideas in plain English.
Documented interfaces make it easier to build responsibly.
Clear contracts — input schemas, result envelopes with provenance, and functions that return N/A instead of Infinity — help developers build tools that are honest about their data. The MCP tool catalog shows the contracts that are candidates for release.
Feedback makes shared tools better for everyone.
Once a reviewed repository is published, issues, pull requests and discussions can improve it. Until then, ideas for safe and useful open components are welcome through the contact form.
What we plan to open
Statuses come from KEYXE’s release manifest. “In Development” means the code exists and is tested in KEYXE’s private repository but has not been released. No license or version is shown until a reviewed release exists.
Read-only tool input schemas and a consistent result envelope, with fully synthetic examples.
Eight tool definitions (accounts_list, datasets_search, dataset_schema_get, analytics_query, reports_create, reports_status_get, audit_events_list, usage_status_get) expressed as JSON Schema, plus a response envelope that always carries source, as-of time, currency, warnings and is_live_amazon_data. Written and tested in the private repository; not yet published.
A deterministic, read-only example client that runs offline against synthetic data.
Planned as a small example that lists tools, validates arguments and prints structured results, with no production endpoints or credentials. It has not been written yet.
A seeded generator of made-up seller, inventory and advertising records. No real Amazon records.
Generates 180 days of fictional data for 24 products in four sample marketplaces and around 100 sample campaigns, with exact reconciliation between levels. Identifiers use non-ASIN prefixes (ZZDEMO, KX-DEMO-). Written and tested privately; not yet published.
Pure functions for ACoS, ROAS, CPC, CTR, conversion rate and illustrative break-even ACoS.
Dependency-free, unit-tested functions that return null instead of Infinity or NaN for undefined ratios. They power the free calculators on this site. Written and tested privately; not yet published.
Helpers that keep tool inputs safe and outputs bounded, and protect CSV exports from formula injection.
Includes CSV cell escaping with spreadsheet formula neutralization, labeled synthetic export envelopes and metric helpers, with tests. Written privately; release review pending.
Guides, a glossary and diagrams that explain commerce analytics and AI tooling.
The eight guides and the glossary are readable on this website now. Publishing them under an open documentation license (for example CC BY 4.0) has not been decided.
What stays private
KEYXE’s public code examples are separate from authenticated customer environments. Credentials, private organizational records, commercial services and Amazon-origin information are not part of our open-source releases.
Public (after review)
Protected (never published)
An MCP interface is not permission to transfer production Amazon data to external AI systems. Real integrations require Amazon authorization and a policy assessment, and live transfer of Amazon data to AI providers is off in KEYXE.
Open core
Some developer tools can be useful independently and may be published under an open-source license. The hosted KEYXE SaaS may include separately maintained proprietary services and paid offerings. We identify the boundary clearly so developers know what they are allowed to use.
Components released under an OSI-approved license can be used, modified and redistributed — commercially too — under that license’s conditions. Nothing has been released yet.
The hosted KEYXE service, its authorization and security systems, and any future paid features. Paid plans are not currently available; see Pricing.
No such commitment is made. KEYXE releases only selected, reviewed components.
Licensing and attribution
Always read the LICENSE and NOTICE files of the specific repository you use. Each released component will state its own license.
For selected original SDKs and tools, KEYXE is considering Apache-2.0, which includes an explicit patent grant and requires keeping copyright and NOTICE information. Documentation may use a separately specified license. No license has been selected yet; until a reviewed release exists, every component on this page shows “Not yet selected”.
Third-party code keeps its original license and attribution, and Amazon-owned code is never relicensed.
The KEYXE name and logos are not covered by any open-source software license; a code license does not grant brand rights.
| Term | What it means at KEYXE |
|---|---|
| Open source code | Code under an OSI-approved license (such as Apache-2.0 or MIT) that allows use, modification and redistribution, including commercial use. |
| Open documentation | Readable public documentation, which may carry its own license (for example CC BY 4.0) once one is chosen. |
| Open examples | Fictional, synthetic datasets created from scratch and cleared for redistribution under a documented license. |
| Source available | Visible code with restrictive terms. KEYXE will not call this “open source”. |
| Private services | Hosted authorization, the credential vault, tenant isolation, billing and commercial data infrastructure. Not published. |
Transparent roadmap
Statuses are local, verified configuration — not live counters. “Last reviewed” dates change only when a status is re-checked or a release happens.
7 items
Read-only tool input schemas and a consistent result envelope, with fully synthetic examples.
Last reviewed Oct 8, 2026
A deterministic, read-only example client that runs offline against synthetic data.
Last reviewed Oct 8, 2026
A seeded generator of made-up seller, inventory and advertising records. No real Amazon records.
Last reviewed Oct 8, 2026
Pure functions for ACoS, ROAS, CPC, CTR, conversion rate and illustrative break-even ACoS.
Last reviewed Oct 8, 2026
Helpers that keep tool inputs safe and outputs bounded, and protect CSV exports from formula injection.
Last reviewed Oct 8, 2026
Guides, a glossary and diagrams that explain commerce analytics and AI tooling.
Last reviewed Oct 8, 2026
Not published. A link appears here only when a reviewed public repository exists.
Last reviewed Oct 8, 2026
Nothing has this status yet.
| Item | Status | Last reviewed |
|---|---|---|
| MCP Tool Contracts | In Development | Oct 8, 2026 |
| MCP Client Starter | Planned | Oct 8, 2026 |
| Synthetic Commerce Data | In Development | Oct 8, 2026 |
| Metric Formulas | In Development | Oct 8, 2026 |
| Testing and Validation Helpers | In Development | Oct 8, 2026 |
| Educational Documentation | In Development | Oct 8, 2026 |
| Public repository | Not published | Oct 8, 2026 |
Contribution guide
Public contributions are not open yet. There is no public repository, so there is nothing to fork today.
Once a reviewed repository is published, contributing will follow the usual flow:
README, CONTRIBUTING, CODE_OF_CONDUCT and SECURITY files will be linked here when they are published. We never expose contributors’ email addresses without consent.
Security and responsible disclosure
Report vulnerabilities through the confidential security form — never as a public issue. A SECURITY.md will point to the same process in any published repository.
Published code never contains production tokens. Example environment files list variable names with obviously fake values only, and every release is scanned for secrets before publication.
Open Source FAQ
No. KEYXE uses a selective open-source approach. Any published repository explains exactly which components are open and under which license. Customer data and private hosted services are not published.
That depends on the license of the specific released component. Code distributed under an OSI-approved license such as Apache-2.0 or MIT permits commercial use subject to its conditions. Review the repository’s LICENSE and NOTICE files.
Public examples use synthetic records and do not grant access to Amazon accounts or customer datasets.
Published examples are read-only and use synthetic data unless a particular integration explicitly documents the lawful authorization process and applicable restrictions. No public sample includes production credentials.
We publish confirmed release dates and links only once a reviewed release is ready. The roadmap indicates the current status.
Software-license permissions do not automatically grant rights to the KEYXE name or logos. Trademark and attribution guidance will be published with the first repository; until then, please ask before using them.
Use our security reporting process rather than publishing credentials or an exploitable vulnerability in a public issue.
Explore our roadmap, learn from the available guides, or share an idea for a safe, useful open-source contribution.
KEYXE is an independent software product operated by ALDER HARBOR IMPORTS LLC.
