Submit an implementation

Send your AIM/AIW metadata. The Store validates it, assigns an Implementation ID, normalizes ResourcePolicies, signs a trust statement and returns the published metadata.

No Implementer ID yet? Register first. To see a valid submission, press Load example below, then Validate only — no credentials needed.

Implementer ID *

Submission token *

The secret string from your registration.

Which AIM does this implement? *

Required to publish, and must match AIMName in your metadata. Everything is validated against the MPAI-AIF V3 schema. Where this Store holds a schema for the AIM you name, it also reports how you differ from that reference build, as non-blocking advisories; it checks the shape of your Implementations and ResourcePolicies, never your numbers.

Implementation name *

Letters, numbers and underscores.

AIM / AIW metadata JSON *

Required keys: Identifier, APIProfile, Description, ExternalPorts, SubAIMs, Topology, Implementations, DataXMData. Your ExternalPorts must match the AIM you declare.

…or upload a JSON file

Used instead of the text box above.

Archive

You host the archive; the Store signs its URL and hash. The URL must match the ImplementationURI in your metadata. ("Validate only" doesn't need it.)

Archive URL

SHA-256

Size (bytes)

How to get the SHA-256 and the size

Linux, macOS or WSL:

sha256sum your-aim.zip     # the 64-character hash
stat -c %s your-aim.zip    # the size in bytes

Windows PowerShell:

Get-FileHash your-aim.zip -Algorithm SHA256
(Get-Item your-aim.zip).Length

Or straight from the published URL:

curl -s -L "YOUR_URL" -o a.bin && sha256sum a.bin && stat -c %s a.bin

The size must match what your server reports.

Authorship signature (hex) — optional, recommended

Proves you authored this submission, not just that you hold the token. Made with your signing key.

How to produce the authorship signature

Run this where your private key lives — the Store never sees it.

MSHA=$(printf '%s' "$(jq -cSa . your_aim.json)" | sha256sum | cut -d' ' -f1)
jq -cSa -n --arg i "YOUR_IMPLEMENTER_ID" --arg m "$MSHA" --argjson a '{
  "download_url":"https://you.example/aims/pkg.tar.gz","sha256":"<64 hex>","size":123
}' '{_type:"mpai-submission",spec_version:"2.0",implementer_id:$i,metadata_sha256:$m,artifact:$a}' \
  | tr -d '\n' > manifest.json
openssl pkeyutl -sign -inkey mpai_key.pem -rawin -in manifest.json -out sub.sig
xxd -p -c 256 sub.sig | tr -d '\n'   # paste this hex into the field above

Keep the a in jq -cSa — it is needed to match the Store's canonical bytes. Requires OpenSSL 3.0+; sign a file, never a pipe.

I confirm I am authorized to submit this metadata, and I understand the MPAI Store publishes and signs the metadata only — it does not host, run, or scan the implementation artifacts, and a listing is not a security endorsement. (See the disclaimer.)

Validate only shows the preview without storing, assigning an ID or signing. No Implementer ID or token needed.

{
  "Identifier": {
    "ImplementerID": "",
    "ImplementationID": "",
    "AIMName": "MMC-TIQ-V2.5"
  },
  "APIProfile": "Basic",
  "Description": "This AIM provides a Text response to a Text and Image query.",
  "ExternalPorts": [
    {
      "Name": "InputText",
      "Direction": "Input",
      "DataType": "OSD-TXO-V1.5",
      "Technology": "Software",
      "Protocol": "",
      "IsRemote": false
    },
    {
      "Name": "InputVisual",
      "Direction": "Input",
      "DataType": "OSD-VIO-V1.5",
      "Technology": "Software",
      "Protocol": "",
      "IsRemote": false
    },
    {
      "Name": "OutputSpeech",
      "Direction": "Output",
      "DataType": "OSD-SPO-V1.5",
      "Technology": "Software",
      "Protocol": "",
      "IsRemote": false
    }
  ],
  "SubAIMs": [],
  "Topology": [],
  "Implementations": [
    {
      "ImplementationURI": "https://aims.example.org/mmc-tiq/2.5/TIQForLinux.zip",
      "BinaryName": "BlipVqaTest",
      "Architecture": "x86-64",
      "OperatingSystem": "Linux",
      "Version": "2.5",
      "Source": "AIMStorage"
    }
  ],
  "ResourcePolicies": [
    {
      "Name": "Memory",
      "Minimum": "2G",
      "Request": "3G",
      "Maximum": "4G"
    },
    {
      "Name": "CPU:Class",
      "Minimum": "Medium",
      "Request": "Medium",
      "Maximum": "High"
    }
  ],
  "Documentation": [
    {
      "Type": "Tutorial",
      "URI": "https://mpai.community/standards/mpai-mmc/"
    }
  ],
  "DataXMData": {
    "DataID": "mmc-tiq-v25-full",
    "Source": [
      {
        "AIMID": "MMC-TIQ-V2.5"
      }
    ]
  },
  "DescrMetadata": "MMC-TIQ-V2.5 reference implementation (FULL). BlipVqaTest is a .NET (C#) console application that answers a natural-language question about an image by running the BLIP visual-question-answering model as three ONNX graphs on the CPU: a vision encoder (~336 MB), a text encoder (~536 MB) and a text decoder (~630 MB), i.e. roughly 1.5 GB of model weights resident in memory. Per section 7 of M3063 (Guide to MMC-TIQ-V2.5 for Linux) the peak working set is 2-2.5 GB, so the deployment guidance is to plan for at least 2 GB of free RAM (3 GB is comfortable), and CPU inference is adequate provided a mid-range or better CPU is available. The declared ResourcePolicies below are exactly those numbers: Memory minimum 2 GiB / request 3 GiB / maximum 4 GiB, CPU:Class minimum Medium / request Medium / maximum High. This is the faithful, unmodified resource envelope of the shipped archive; a companion instance (ImplementationID TIQ-LITE-1) declares a reduced envelope for the same archive. The ImplementationURI points at the implementer's own storage; the Store signs the URL and the SHA-256 the implementer declares for it."
}