--- name: getnuans description: Help customers obtain Canadian NUANS reports and related proposed-business-name searches for incorporation planning, corporate name changes and name reservations. Use for product selection, validated quotes, authorized GetNuans MPP purchases and report tracking; GetNuans does not perform incorporations or government filings. --- # GetNuans ## When to use this skill Use this workflow when a customer wants a NUANS report or a supported name search through GetNuans. For an existing order, go directly to status lookup rather than starting another purchase. GetNuans is an independent Canadian NUANS report and name search service, not a government registry. It does not incorporate companies or file registration applications. A report does not guarantee name approval or registration, and buying one does not establish a company. Refer filing or legal questions beyond this scope to the applicable registry or an appropriate professional. Use either the REST Agent API below or the equivalent tools at the [GetNuans MCP endpoint](https://api.getnuans.com/mcp): `list_products`, `create_quote`, `create_purchase_link` and `check_order_status`. Both interfaces share current product requirements and validated ordering. MCP purchase-link generation only returns HTTP POST payment instructions; it does not submit payment or check quote validity. Payment still requires an MPP-capable HTTP client and authorized wallet. See the Agent Guide for connection details. ## Discover products and requirements Before preparing a new order, call `GET https://api.getnuans.com/api/agent/products`. Treat that response as authoritative for current availability, product IDs, prices, currency, jurisdictions, required and optional fields, legal endings, purposes, defaults, conditional requirements and other published restrictions. Use the exact API-compatible option values, not remembered labels or general incorporation knowledge. Never maintain a separate catalog, price list or dropdown list. Different jurisdictions can have different rules. Use the [OpenAPI specification](https://getnuans.com/api/agent/openapi.json) for exact request and response structures and the [Agent Ordering Guide](https://getnuans.com/agents) for integration details. All ordering API requests go to `https://api.getnuans.com`, not the website host. If product metadata is unavailable, do not invent current prices or requirements. If live metadata and documentation conflict, resolve the inconsistency before initiating payment; do not guess or bypass validation. Clarify the customer's intended jurisdiction and purpose when unclear. Distinguish an initial name search from a jurisdiction-specific reservation report; do not assume every customer needs a report or that Ontario is the intended jurisdiction. Select only a currently available product that matches the customer's request. Do not claim a report is legally required without authoritative context. ## Collect and validate customer information Collect the selected product's applicable fields using its current definitions and the OpenAPI wire names. Reuse information already supplied; ask only for missing or ambiguous details. Never invent customer names, email addresses, proposed names or business activities. - Preserve the customer's intended name, spelling and business activity. Follow the product's name-assembly and normalization requirements; do not arbitrarily add, remove or duplicate a legal ending. - Retrieve the product's legal ending options and check whether an ending is required or omission is allowed. Use the customer's selection and the exact returned value; never transfer one jurisdiction's choices to another. - Retrieve that product's purpose options. Match the customer's actual purpose to an allowed value; clarify intent instead of inventing a generic purpose. When using localized product metadata, send the corresponding locale in the quote. - Follow every other published required field, optional field, dependency and restriction. An initial form default is not permission to invent missing customer information or silently replace an invalid choice. Where distinctive terms apply, use the published field (`request.distinctiveElement` in the current contract) and terms actually present in the proposed name. For `Northstar Digital Solutions Inc.`, `Northstar Digital` illustrates containment; `Blue Harbor` does not. Do not assume a partial word is acceptable. Follow the server's normalization and token-boundary rules, and do not require this field for a product that does not require it. The Quotes API makes the final validation decision; do not recreate its validator. ## Obtain an immutable quote Call `POST https://api.getnuans.com/api/agent/quotes` with the discovered product ID and collected inputs, following OpenAPI. Inspect the response before continuing. For a validation error, inspect its field-specific details, refresh product metadata when relevant, and obtain corrected customer input if needed. Submit a corrected request rather than repeatedly retrying identical invalid data. Resolve validation errors before requesting payment. A successful quote fixes the validated order details and quoted amount and creates an unpaid database record. Keep the Quote ID private. Creating a quote does not charge the customer or start report processing. If the customer changes material information, obtain a new quote rather than altering details at payment time. If payment for the previous quote was attempted or its outcome is uncertain, reconcile that attempt first to avoid a duplicate purchase. ## Authorize and complete payment Present the selected product, relevant order details, quoted total and currency. Explain that proceeding initiates a paid purchase and obtain authorization for that specific purchase through the available client workflow. An information request is not purchase authorization. Preserve valid authorization already obtained; avoid repeated confirmation loops while respecting any additional payment-system approval. Use `POST https://api.getnuans.com/api/agent/orders` with only the validated Quote ID as defined in OpenAPI. Follow the existing HTTP 402 challenge and MPP-compatible client workflow described in the Agent Guide; do not implement a separate payment mechanism. Use an authorized Stripe Shared Payment Token (SPT) for the quoted seller, amount and currency. The integration supports Card and Link configurations, subject to the deployed challenge, Stripe account eligibility and client capabilities. Follow the methods actually advertised by the response; do not claim an unavailable method or an unperformed payment test succeeded. Card-backed tokens issued through Link Agent Wallet remain Card payments; Link-backed tokens use the Link payment method. - Create one idempotency key for the quote and reuse it unchanged for the initial request and retries of that purchase attempt. Follow the guide's exact requirements. - Echo the signed challenge unchanged. For uncertain outcomes, retain the original quote, idempotency key and credential rather than obtaining a new payment attempt or starting a second purchase. - Never collect card numbers or security codes in ordinary chat. Use the supported secure client authorization mechanism; never invent an SPT. Do not expose payment credentials in messages, logs or shared artifacts. - Require confirmed payment/order acceptance before reporting a purchase. An authentication-required, failed or incomplete payment is not success. Use the issuer/client's supported authentication process where available. - If the environment cannot complete MPP, explain the limitation without claiming an order was placed. Do not create another Checkout flow, payment link, payment rail, account system or ordering endpoint. ## Track and retrieve the report Preserve the returned Order ID and the customer's actual email. Payment confirmation and order acceptance precede asynchronous processing; neither means the final PDF is ready. Call `POST https://api.getnuans.com/api/agent/orders/status` with Order ID and customer email using the current OpenAPI structure. For an uncertain payment outcome, the original challenge's `externalId` also identifies the order as described in the guide. Do not invent identifiers or status values. Follow returned polling guidance, including `poll_after_seconds` and `Retry-After`, rather than making excessive repeated requests. Distinguish accepted, processing, completed and failed outcomes using the actual contract. Do not claim report completion or delivery before the response confirms it. When a completed report is downloadable, use the returned protected download URL unchanged. If a URL expires, repeat verified status lookup for current download information rather than constructing another URL. Keep customer email, quote identifiers, credentials and protected download links private. The existing customer portal, email delivery and support remain available; do not add authentication or delivery systems. ## Handle errors without duplicate purchases - Fix invalid or missing fields before quoting again; do not bypass the Quotes API. - Respect rate limits and `Retry-After`. Explain unavailable discovery or quoting instead of supplying guessed data. - Treat conflicts, expired quotes and uncertain provider/network errors according to the guide. A temporary error does not prove no payment occurred. - Check the original Order ID and email before considering another purchase after a payment attempt. If the outcome cannot be determined, contact existing GetNuans support and stop new purchase attempts until it is resolved. - If a quote expired before any payment attempt, refresh discovery and request a new quote. Reconfirm authorization if the product, details or quoted total changed. - Explain processing delays or failures accurately. Do not promise a successful name approval, refund or report delivery that has not been confirmed. ## Authoritative references - [Products API](https://api.getnuans.com/api/agent/products): current products, prices, field requirements, options and restrictions. - [OpenAPI specification](https://getnuans.com/api/agent/openapi.json): exact API contract; the Quotes API performs authoritative validation. - [Agent Ordering Guide](https://getnuans.com/agents): detailed MPP, retry, status and delivery instructions. - [GetNuans website](https://getnuans.com): customer-facing service information and access to existing support and order tracking.