Introduction
This guide will walk you through managing AI Card requests to other organizations using the Outgoing Requests tab in the AI System Manager. AI Cards are a convenient way to aggregate AI System artifacts like compliance frameworks and bills of materials. A publisher can also choose to share vulnerability data on an AI Card. A request can repeat on a schedule, so the publisher is asked for an updated AI Card each cycle. Following these steps, you can send requests for these artifacts to publishers, allowing for smoother collaboration and improved compliance management.
Entry Point
AI System Manager
From the AI System Manager, click the Request AI Card button.
Creating an AI Card Request
Input Request Details
In the Request Name field, provide a unique name for your request. We recommend including the name of the AI System in the Request Name. In the Due Date field, you can select a date as the deadline for response. Due Date is optional. In the Request Details, specify the context of your request and any other important details for the publishing organization.
Refresh Schedule sets how often the publisher is asked for an updated AI Card. The options are:
- None: The request is sent once and does not repeat.
- Update Monthly: The publisher is asked for an updated AI Card every 30 days.
- Update Quarterly: The publisher is asked for an updated AI Card every 90 days.
- Custom: The publisher is asked for an updated AI Card at the interval you enter in Repeat Every (Days). Enter a whole number from 7 to 90.
The form starts at Update Quarterly. Choose None for a one-time request.
When a request has a refresh schedule and Due Date is blank, the first due date is the send date plus one period. Each time the publisher sends an update, the next due date is set one period after that update. If Cranium has turned on reminders for your organization, the publisher receives email reminders timed from the due date.
Next, click the blue Continue button to move on to the card configuration.
Configure the AI Card
Select the artifact requirements you want to include to configure the AI Card for your request. You can start by choosing the Compliance & Trust box to specify Compliance Framework requirements. This action will display a dropdown menu where you can multi-select frameworks or search for specific ones by name. Next, you can select the Bill of Materials box if your request includes a Bill of Materials (BOM). This will open a Description field for describing the BOMs you would like to receive. If you want the publisher to share vulnerability data with the AI Card, say so in this Description field. The publisher decides whether to share vulnerability data when they publish the card. Lastly, you can select the Additional Documentation box if you want the responding organization to include any supplemental documents. Configure these options as needed to ensure the AI Card aligns with your request requirements. Then, click the blue Continue button to move on to publisher details.
Complete Publisher Details
Finally, choose the organization and the person who will receive the request. Search Publisher Vendor to find one of your vendors. Then choose a Contact to receive the request. If the person is not yet a contact for that vendor, add them as a new contact. The request is filed under the vendor you chose, and a new contact is saved to that vendor. Retired vendors and their contacts do not appear in these lists.
If the organization is not one of your vendors, select Vendor not listed? Enter a new one. The form will expand, allowing you to input the organization's name and the contact details of the user who will fulfill the request.
Once all fields are filled, click the blue Create Request button to submit. The dialog will close, and your request will appear in the Outgoing Requests table with a Pending status. The publisher will be notified via email.
Monitoring Outgoing Requests
The Outgoing Requests table displays all requests you've sent to other organizations. Use this table to track the status of your requests and identify which organizations still need to respond. The table displays:
- Name: The AI System name you're requesting information about
- To: The organization name and user email receiving the request
- Date Sent: When you sent the request
- Due Date: The deadline for the response. A tag in this column shows how close the date is: Due in N Day(s), Due Today or Overdue. A completed request on a refresh schedule also shows the tag while its next update cycle is open.
- Details: Brief description or notes about your request
- Refresh Schedule: How often the publisher is asked for an updated AI Card. Requests with no schedule show None, including every request sent before refresh schedules were available. Select the history icon next to the schedule to see how it has changed.
- Status: Current status, such as Pending or Completed. A completed request on a refresh schedule shows Completed · Update Pending while the publisher's next update is open, and Completed · Update Overdue once that update is past its due date. Other completed requests show Completed.
You can sort by any column to organize your outgoing requests by date, recipient, or status.
Changing a Refresh Schedule
You can add, change or remove the schedule of a request you already sent. In the Refresh Schedule column, select the pencil icon next to the request's schedule to open Edit Refresh Schedule, then choose the new schedule. The change takes effect next cycle. The current due date does not change.
Requests sent before refresh schedules were available have no schedule. You can add a schedule to these requests in the same way.
Viewing Refresh Schedule History
The history shows who changed a request's refresh schedule, when and how. In the Refresh Schedule column, select the history icon next to the request's schedule to open Refresh Schedule History. Each change is listed with these fields:
- When: When the change was made.
- Changed by: The name of the person who made the change, or Deleted user, Unknown user or System.
- What changed: The change made to the schedule.
A request with no changes shows "No refresh schedule changes recorded." The history starts with release 2026.11.1, so earlier changes are not listed. Only your organization sees this history. The publisher does not.
Filtering Outgoing Requests
Filters narrow the table to the requests you want to follow up on. Click Filters above the table to open them.
- Status: Shows only requests with the statuses you select. Completed, Completed · Update Pending and Completed · Update Overdue are separate options. Completed covers only requests with no update cycle open, so it does not include requests whose next update is pending or overdue.
- Refresh Schedule: Shows only requests with the schedules you select: Monthly, Quarterly, Custom or None. None includes requests that never had a schedule.
Reminding Publishers to Respond
Reminders keep your request in front of the publisher until they respond. Reminders are opt-in. Cranium turns them on for each requesting organization, and there is no setting for them in the platform. If reminders are not turned on for your organization, publishers do not receive reminders, even for requests with a due date.
When a request has a Due Date, the publisher receives an email reminder to publish an AI Card at these points:
- One week before the due date
- On the due date
- One day after the due date
Each reminder email shows the request's due date. When a request has a refresh schedule, the publisher receives these reminders for each cycle, timed from that cycle's due date. When a request has no due date and no refresh schedule, reminders follow a deadline a fixed number of days after the request was created. Cranium sets the number of days for your organization.
Reminders stop once the publisher responds to the request. If you request changes to the AI Card, reminders start again. Changing a request's refresh schedule to None stops reminders for the current cycle at once. The current due date stays as it was. Requests created through the API have no refresh schedule unless one is set.
Reviewing Received AI Cards
When a publisher responds to your request, you'll receive an email notification that an AI Card has been shared. Navigate to the Received AI Cards tab to review the submission. Click the Review AI Card button on any card to open the review panel.
The review panel shows the publisher information, primary contact, and the artifacts included in the AI Card response. Review the Compliance Frameworks, Bills of Materials and Additional Documentation that were provided. Some AI Cards published earlier also include vulnerability report PDFs, which you can still view and download.
At the bottom of the review panel, you have three options:
- Decline: Reject the AI Card
- Request Changes: Send feedback requesting modifications to the AI Card
- Accept AI Card: Accept the AI Card as provided
Reviewing Shared Vulnerability Data
Shared vulnerability data shows you the known vulnerabilities in the AI System behind the card, as the publisher last reported them. When a publisher shares vulnerability data, the card tile shows a Vulns (N) panel. The panel has a model chart and a technology chart that count findings by severity.
The card details include these tabs:
- Model Vulnerabilities: Findings for the models in the AI System.
- Technology Vulnerabilities: Vulnerabilities in the technology the AI System uses, including CVEs. The AI column marks AI-related vulnerabilities. Select Show AI vulnerabilities only to hide the rest.
Shared vulnerability data is a snapshot taken when the publisher publishes or updates the card. It includes CVEs, model findings, resolved findings and their resolution reasons. It does not include who resolved each finding, the AI System, the project name or the repository name. You cannot act on these findings. Newer results appear only after the publisher updates the card.
The same views appear for the card under My Vendors.
Requesting Changes
If the AI Card doesn't fully meet your requirements, click the Request Changes button. A popup will appear where you can type specific feedback about what modifications you need. Once you submit your change request, the card's status remains Pending and the publisher is notified via email about the requested changes.
Accepting an AI Card
Once you accept an AI Card, the Review AI Card button changes to View Details, allowing you to reference the card's contents at any time.





