Positioning
WAO is an AI Performance Intelligence Platform, not an AI model.
Waltrump AI OrchestratorResources
Public resources explain WAO positioning, benchmark workflows, Gateway readiness, enterprise value, security posture, and support paths.
Resource Center
Understand the public WAO journey before requesting an invite.
Open resourceLearn how prompt datasets become benchmark evidence before deployment.
Open resourceUnderstand AI Health Score, maturity, confidence, evidence coverage, and recommendations.
Open resourceReview API keys, provider abstraction, production monitoring, and gateway intelligence.
Open resourceCompare execution, credential, data, delivery, access, and maturity boundaries.
Open resourceUnderstand Benchmark Express, stability, cost, scorecards, actions, readiness, visibility, authenticity and Capture.
Open resourceUnderstand exact provider/model/operation activation for text, embeddings, image, audio, video and proposal-only agents.
Open resourceReview application packs, proposal-only tool behavior, human approval and remaining acceptance limitations.
Open resourceUnderstand credential, execution, artifact, consent, safety and audit boundaries.
Open resourceWalk through the pilot-friendly product experience.
Open resourceReach Waltrump Technology for pilot or launch support.
Open resourceTrust Topics
WAO is an AI Performance Intelligence Platform, not an AI model.
WAO should explain score, maturity, evidence coverage, confidence, and improvement guidance.
Network participation is opt-in and privacy protected.
Provider/API costs may be separate.
Controlled-beta status
These states come from the server capability catalog. They are not purchase, certification, global execution or scale-readiness claims.
36 capability records
Evaluate submitted evidence with a bounded evaluation pack
Submit evidence to a supported pack for a scoped evaluation.
What you get: A pack evaluation result for the submitted evidence.
Provider and agent runs remain separately activated.
When to use it: Use it when a defined pack fits the evidence you already have.
Illustrative example: Evaluate submitted examples using an eligible pack before discussing the findings.
Connect an approved project to a scoped provider request
Configure an exact project grant and bring your own provider API key for an eligible Gateway request.
What you get: A response to the specifically authorized request under current controls.
Provider execution remains default off and requires current controls.
When to use it: Use it when an approved application needs an eligible provider path.
Illustrative example: A project administrator requests activation for one provider and operation before a request is made.
See how your AI is performing and what needs checking
Bring available evaluation results into a scoped health review and see where evidence is missing.
What you get: A review of measured findings and testing gaps to help you choose what to investigate next.
Decision support for measured evidence; missing dimensions remain unmeasured.
When to use it: Use it when you need a concise view before expanding an AI workflow.
Illustrative example: A support assistant has evidence for common questions but not refund exceptions; review the gap before deciding what to test.
Turn a health finding into an accountable next step
Record an action against a scoped health finding, then review applicable evidence of completion.
What you get: A saved action and evidence-based verification state for follow-up.
An action is verified only with applicable evidence.
When to use it: Use it when a health review identifies an issue someone needs to address.
Illustrative example: Assign a coverage gap to an owner and check the supporting evidence before marking it verified.
Review a declared performance band in a private pilot
Provide declared information for a reviewed enterprise assessment with required consent and privacy controls.
What you get: A saved declared-band assessment for the pilot.
Requires enterprise provisioning, consent and privacy thresholds; not real peer-performance proof.
When to use it: Use it when a provisioned enterprise is assessing its declared performance band.
Illustrative example: A participating team reviews its declared band without claiming verified peer performance.
See which readiness questions still need supporting evidence
Provide declarations and available evidence for a scoped readiness review.
What you get: A saved readiness view that separates declared answers from supporting evidence.
Declared answers do not replace measured evidence.
When to use it: Use it when a team needs to organize readiness questions before a review.
Illustrative example: A team records its review process and identifies where evidence has not yet been attached.
Review safety signals without treating them as guarantees
Review safety evidence within the scope of your evaluation.
What you get: A view of available safety signals and their limits for human review.
Safety signals are not a guarantee of safe operation.
When to use it: Use it when safety is part of a decision about an AI workflow.
Illustrative example: Review the evidence from a set of safety cases before deciding which cases need more testing.
Inspect saved observations and the citations behind them
Review previously saved observations and citations within the approved scope.
What you get: A view of retained observations and their cited sources.
New external observations require separate exact activation.
When to use it: Use it when explaining what supported a previous observation.
Illustrative example: Review saved citations for an earlier observation before discussing its implications.
Invite-only Manual plan assignment Payments and checkout disabled Capabilities and quotas vary by approved plan
Review integration boundaryInvite-only Controlled provider execution may be disabled per environment Quota and policy enforced No browser or mobile key storage
Review integration boundaryInvite-only Server-side use only Modes and quotas vary by plan Customer must review critical recommendations
Review integration boundaryInvite-only Server-side use only Templates and quotas vary by plan Reports describe supplied evidence and are not certifications
Review integration boundaryManual approval Controlled download only Not published to public registries Version, expiry, support, and revocation are grant-controlled
Review integration boundaryEnterprise design-partner pilot only No self-service download Real customer installation evidence required Licence, quota, version, expiry, support, and revocation controlled
Review integration boundaryDo not request, sell, provision, implement, or imply availability
Review integration boundarySecurity boundary
Public materials do not expose credentials, raw customer evidence, scoring formulas, evaluator instructions, hidden provider logic, or other protected methods.
Public FAQ
No. The 23 factors are WAO's performance taxonomy. Each workflow measures only applicable factors and identifies missing or insufficient evidence.
No. WAO remains invite-only, payments and checkout are disabled, and expanded capabilities require review.
No. Private deployment is a design-partner discussion and controlled pilot path.
No. Contribution is off by default and requires explicit consent; insight access and contribution are separate.
Authenticated customers can open Customer Help inside the WAO application after sign-in.
Invite-only Beta
Start with one benchmark, review AI Health, and use evidence-based recommendations to improve before you scale.