Copy / share
For AI agents
How to evaluate Momentum AMP certificate and task automation
Separate the requested task, certificate preview, issued result and destination readback. Start with one insured, policy term and holder, then decide which evidence proves the specific action complete.
Use the evaluation ledger
On this page
Choose a certificate or task outcome
Momentum AMP’s public application programming interface (API) separates list queries from operations. Its landing page lists certificate-holder and task categories; those labels do not tell you which action your agency may perform. Begin with one outcome: prepare a certificate preview, obtain an issued artifact, change a task assignee or confirm a task’s recorded state.
As checked October 6, 2026, the public footer displays API v2.2.1.77. The migration FAQ still announces September 30, 2026 legacy retirement. Treat that as the published schedule, not proof that a legacy connection has stopped or that Decla has migrated. Record the actual interface and environment selected for your evaluation.
Sources
- Momentum AMP Public API overview — accessed
- Momentum AMP migration FAQ — accessed
Match the operation to its evidence
| Boundary | Public contract reference | Evaluation consequence |
|---|---|---|
| List retrieval | The guide describes read-only Open Data Protocol (OData) collections, including CertificatesList, CertificateHolderList and MasterCertificateList. OData is a query interface. | Use retrieval to identify the record and check the chosen source period. A returned list is not permission to issue, distribute or modify a certificate. |
| Certificate preview | The guide lists POST /api/SendCertificate/PreviewCertificate and GET /api/SendCertificate/DownloadPreview/{historicalCertificateHolderId}. | Agree the holder reference and preview inputs before review. A preview file is not an issued result or evidence of delivery. |
| Task assignment | The guide lists POST /api/Tasks/UpdateAssignedTo. | Inspect the selected task and permitted assignee, then compare the resulting assignment. Assignment does not establish certificate issuance or task completion. |
| Legacy checklist | The guide identifies the legacy workflow-checklist area as absent from the new API. | Check any checklist dependency before testing. Do not assume a task list or an assignment operation replaces that workflow. |
Freeze the records and source edition
Keep the insured, policy, policy term, holder and task references together. Record when the source was retrieved and which packet edition it supports. Confirm the agency context, current holder details and the policy period against the authorized source; a matching display name alone cannot distinguish records or renewal terms.
Name the permitted action and reviewer before supplying data. Read access, preview preparation, issuance, distribution and task updates require separate scope decisions. Keep credentials out of the evaluation ledger. If the detailed request or response fields for your selected operation are unavailable, record that gap rather than inventing a payload.
Run one bounded evaluation
Define the completion check
Agency process owner
Choose one outcome and observable evidence. For a preview, inspect the file against the request. For an issued result, require the resulting artifact and applicable destination state. Define distribution and task closure separately.
Confirm the source and interface
Agency administrator
Record the current public contract, selected environment, exact entity references and source period. Resolve missing permissions or changed legacy mappings with the agency administrator before an authorized test.
Review the exact edition
Agency reviewer
Compare the holder, policy term and source packet with the proposed artifact. Record the reviewer’s disposition and the action it covers. A changed holder or request edition requires a new comparison and disposition.
Record the attempt and response
Authorized operator
Only an authorized operator performs the agreed action. Capture a sanitized request reference, time, response and any returned object reference. An acknowledgement or success response belongs in the attempt record; it does not replace the completion check.
Compare the destination
Agency reviewer
Match the resulting artifact or destination readback to the approved entity, holder, term and edition. For a task update, compare the actual assignee or state. Leave unproven delivery, closure or other actions open and assign the next check.
A changed holder with a partially closed task
| Stage | Fictional record | Check | Disposition |
|---|---|---|---|
| Planned request R1 | Insured I1; policy P1, term October 1, 2026–October 1, 2027; holder H1; packet S1 dated October 6, 2026; task T1. | Requested outcome: reviewed certificate for that tuple; delivery is a separate action. | Planning only; no action performed. |
| Initial retrieval | L1 points to the prior term, October 1, 2025–October 1, 2026, for insured I1. | The insured matches but the policy period does not. | Hold; do not reuse prior-term information as current. |
| Corrected source | L2 identifies P1’s October 2026–2027 term and H1; retrieved October 6, 2026 against S1. | Compare the record references and period with R1. | Source match recorded; proceed only within agreed preview scope. |
| Preview review | V1 corresponds to R1/H1/P1; review RV1 covers this preview edition only. | No issued-result or distribution permission is recorded. | Preview reviewed; issuance and delivery remain open. |
| Changed request | R2 changes holder H1 to H2. | V1 and RV1 belong to the superseded holder edition. | Hold action; rebuild the comparison and obtain a new disposition. |
| Fictional issued result | V2 matches R2/H2/P1; RV2 explicitly permits the selected issuance action. Authorized operator records issued artifact C1. | Compare C1’s holder and policy term with R2 and S1. | Issued-result evidence matches in this example; no delivery receipt is supplied. |
| Separate task readback | Readback B1 matches C1/R2/H2/P1; T1 is assigned to the servicing coordinator and remains open. | The recorded task state is not closed, and delivery is still unverified. | Partial closure only; coordinator owns delivery verification and task follow-up. |
Stop on a mismatch; preserve the unresolved outcome
- If a holder, policy term or source edition changes, preserve the old reference for comparison and review the new edition. Do not carry a superseded disposition forward.
- If a response is missing or ambiguous, inspect the prior attempt and destination before retrying. Resolve duplicate or conflicting objects with the authorized owner; a generic retry rule does not establish that a certificate action is safe to repeat.
- If the artifact matches but delivery or task state does not, record a partial result and the next owner. Do not mark the whole service item complete from the certificate reference alone.
Source scope and next check
The public migration guide is dated July 29, 2026; its list and certificate/task mapping was checked October 6, 2026. It documents an interface, not the agency’s deployed configuration, a coverage decision or actual Decla support.
Use this ledger with your agency’s authorized source and review procedure. For a proposed Decla task, request current evidence for the exact operation, grant, approved input and destination result before treating it as available.
Sources
Frequently asked questions
How do I evaluate certificate and task automation in Momentum AMP?
Separate the requested task, certificate preview, issued result and destination readback. Start with one insured, policy term and holder, then decide which evidence proves the specific action complete.
What is Decla?
Decla is AI software for independent insurance agencies and brokerages. It connects to your AMS, email and carrier portals and does back-office work inside them. Your team reviews the work before it goes out.