MentionBird

compliance_requirements

What one country asks for before it will approve one registration, with where each item stands and why any was refused. `sms_senders_requirements` says which countries want a registration; this says what one is asking for, addressed by that row's `registration_id` as `subject_id`. Without `subject_id` it answers the form with no submission behind it, every item unanswered except those `identity_id` prefills, and `program` turns required, because a country can run more than one and there is no registration to read it from. `satisfied` is whether every required item is approved or not applicable; `needs_input` separates items still waiting on you from answers already with a reviewer.

Remote bird/mcp

Remote (network-hosted)

Other tools also called compliance_requirements? See providers with this name

Input Schema


            {
  "type": "object",
  "properties": {
    "program": {
      "type": "string",
      "description": "The programme to read. Optional alongside subject_id, because a registration is under exactly one programme and that is the one used; supply it there only to confirm the programme you expect, since one that is not the registration's own returns a 422, as does supplying one at all for a country that runs no registration programme. Required when subject_id is omitted, because there is then no registration to resolve it from and a country can run more than one."
    },
    "subject_id": {
      "type": "string",
      "description": "The registration to answer for. Omit it to read the form on its own, before you hold anything to register: the requirements come back unanswered, which is what to do when you are deciding whether to take a number or a sender on in the first place. Omitting it makes program required, since the coordinate is otherwise resolved from the subject. When you do supply it, it is an scr_ id when subject_kind is sms_sender and an nda_ id when it is number."
    },
    "identity_id": {
      "type": "string",
      "description": "Prefill the business details from a party you have already described. Requirements that ask about the party come back carrying its answers, marked prefilled; requirements about this sender never prefill because you write the sender's intended use fresh each time. Anything you have already filed for this registration wins over the party's answer."
    },
    "country_code": {
      "type": "string",
      "description": "The destination country."
    },
    "subject_kind": {
      "type": "string",
      "examples": [
        "sms_sender",
        "number"
      ],
      "description": "What you are registering."
    }
  }
}