> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/wip-social-registry-v1.0.0/social-registry/1.-crvs/1.2-process/prs.sr.01-sp-mis-queries-the-social-registry-to-verify-eligibility-for-programme-enrolment.md).

# PRS.SR.01: SP-MIS queries the social registry to verify eligibility for programme enrolment

This use case relates to the intake stage of the social protection delivery chain. Its purpose is to provide information that the SP-MIS needs to verify if a beneficiary or household is eligible for the social protection scheme. The beneficiary in this use case may be an individual, a household or another type of entity.

This use case applies in cases where the SP-MIS proactively requests a list of potential beneficiaries from the social registry that meet specific eligibility criteria to initiate enrolment in a programme. Or it may be reactive when a potential beneficiary requests enrolment in the scheme, prompting the SP-MIS to query the social registry to retrieve additional information on the potential beneficiary or their household/family to verify their eligibility. 

The [DO.SR.03 Group](/standards/dci-standards/wip-social-registry-v1.0.0/social-registry/1.-crvs/data/data-objects/do.sr.03-group.md)and [DO.SR.02 Member](/standards/dci-standards/wip-social-registry-v1.0.0/social-registry/1.-crvs/data/data-objects/do.sr.02-member.md) data objects list the attributes that the SP-MIS can use to request a list of beneficiaries as well as the attributes that may be returned to provide the data needed to verify eligibility. 

The request to share data will be initiated by the SP-MIS (possibly alongside requests to other registries) to verify eligibility. This could be a request for an individual potential beneficiary or a group (household or family) depending on the unit that benefits from the programme and the programme’s eligibility criteria) or it could be a bulk request for a batch of individuals or groups. 

The social registry will respond with the requested information on the potential beneficiary(ies). 

Please refer to the sub-pages for descriptions that illustrate this generic use case using examples from common social protection programmes/schemes.  

## API Reference 

* [Search API](https://api.spdci.org/release/html/social_api_v1.0.0.html#tag/Sync/operation/post_reg_sync_search)
* [Notification API](https://api.spdci.org/release/html/social_api_v1.0.0.html#tag/Sync/operation/post_reg_sync_notify)
* [Transaction Status API](https://api.spdci.org/release/html/social_api_v1.0.0.html#tag/Sync/operation/post_reg_sync_txnstatus)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://standards.spdci.org/standards/dci-standards/wip-social-registry-v1.0.0/social-registry/1.-crvs/1.2-process/prs.sr.01-sp-mis-queries-the-social-registry-to-verify-eligibility-for-programme-enrolment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.