Verify New Zealand Business

Produce a Chinese-language, evidence-backed initial verification report. Separate official facts, consistency observations, risk signals, unknowns, and recommended follow-up checks.

Workflow

1. Collect at least one identifier:
   - legal or trading name;
   - 13-digit NZBN;
   - New Zealand company number;
   - website, email, quotation, invoice, or contact details.
2. Prefer the official NZBN API:
   - Set NZBN_API_KEY in the runtime environment.
   - Run python3 scripts/verify_nz_business.py lookup --nzbn <NZBN> for an exact NZBN.
   - Run python3 scripts/verify_nz_business.py search --name "<NAME>" for name candidates.
3. If API access is unavailable, use the official NZBN and Companies Register search pages manually. Never invent missing register data.
4. Save the official entity JSON, then run:

python3 scripts/verify_nz_business.py assess --entity entity.json --website https://example.co.nz --email person@example.co.nz

5. Review the generated JSON against references/report-schema.md.
6. Return a concise Chinese report with source URLs and retrieval time.

Evidence Rules

• Treat NZBN and Companies Register data as authoritative registration evidence, not proof of solvency, honesty, current trading activity, or transaction safety.
• Use the legal entity name, NZBN, entity type, status, registration source, addresses, trading names, website, and public contact details when available.
• Mark voluntarily supplied or absent fields as such. Absence of a website, phone number, trading name, or industry code is not by itself evidence of fraud.
• Distinguish a registered company from sole traders, partnerships, trusts, public entities, and overseas companies registered in New Zealand.
• Report ambiguous name matches instead of selecting one silently.
• Never report directors, shareholders, licences, insolvency events, sanctions, court records, or financial-service permissions unless those facts were checked in the relevant official source.
• Never expose API keys, authentication headers, private register data, or unnecessary personal information.

Risk Classification

Use only these outcomes:

• 信息一致，未发现明显异常: official record found and supplied details materially align.
• 需要补充核验: official record exists but important fields are absent, ambiguous, or not independently matched.
• 发现不一致或风险信号: one or more material conflicts exist.
• 无法完成核验: no reliable match, source unavailable, or evidence insufficient.

Do not use “绝对真实”“安全可靠”“诈骗公司” or equivalent definitive claims.

Website and Contact Checks

Compare, without overclaiming:

• website host against the entity's public website;
• email domain against the website host;
• legal/trading name against the website identity;
• supplied address and phone against public register data;
• quotation or invoice payee name against the registered entity.

Flag free-email addresses, unrelated domains, recent redirects, copied identities, or requests to pay an unrelated account as follow-up signals only. They require additional evidence.

Output

Follow this order:

1. 核验结论
2. 官方登记信息
3. 一致性检查
4. 风险信号与未知项
5. 建议补充材料
6. 证据来源与查询时间
7. 免责声明

Keep the report useful to a mainland Chinese buyer. Explain New Zealand entity terms briefly instead of translating labels mechanically.

References

• Read references/quickstart.md for a complete Chinese example, manual fallback, and FAQ.
• Read references/official-sources.md before adding or changing a data source.
• Read references/report-schema.md before changing report fields or classification.
• Read references/market-boundary.md before broadening this skill into another country, credit scoring, legal advice, or a different industry.