Content and editorial policy
Who publishes 1ZheAI content, how we use sources, disclose commercial interests and handle corrections.
Publisher and contact
1ZheAI publishes this website, its documentation and blog. Blog bylines identify the credited author; 1ZheAI maintains the documentation. Contact [email protected] about content or services.
Commercial interests
1ZheAI sells model API access, AI accounts and subscription services, and sources some products through upstream distribution. Content about our products has a commercial interest and is not an independent third-party review. Brand mentions do not imply a partnership or official authorization unless explicitly stated. Paid promotions, sponsorships and commission links should be disclosed beside the relevant content.
Sources and original work
Use official documentation or direct sources for features, pricing and rules. Experiments should specify versions, dates, methods, results, limits and reproduction steps. Separate source facts from our analysis. Rewriting another article or making an unverified inference does not substitute for testing.
Documentation, news and analysis
Documentation helps readers complete a task. The blog may publish integration experiments, analysis and product news. Only reporting on recent events belongs in news. Tutorials, promotions and old articles do not become news by changing a label or date. Headlines and summaries must match the article.
Dates and revisions
Keep the original publication date. Change the editorial modification date for substantive revisions, not migrations, rebuilds or metadata edits. Major factual corrections should explain what changed, why and when. Describe client verification separately: checking a configuration is not an end-to-end API test.
AI assistance and translation
AI may assist with drafting, translation or code. Its output is not a factual source or proof of a real API test. Claims, results and quotations still need supporting evidence, with unverified scope stated. Do not invent authors, qualifications, interviews or test results.
Corrections
Email the page URL, the disputed passage, a suggested correction and checkable evidence. We will assess the issue and correct the original when needed. Never send passwords, full API keys, sessions, redemption codes or identity documents.