This guide describes how credits are used for parsing, indexing, and search operations in RChilli’s Search & Match service.
1. Indexing a Document
When you index a document, 2 credits are deducted per document:
- Parsing (1 credit+ 1 extra if OCR document): Extracts structured data from the document (resume, job description, etc.). Parsing alone does not make the document searchable.
- Indexing (1 credit): Makes the document searchable and available for match operations.
Example:
Uploading a resume for indexing consumes:
- Parsing = 1 credit
- Indexing = 1 credit
Total = 2 credits [1 extra for OCR Document]
2. Search & Match Operations
- Performing searches on indexed documents does not consume any credits.
- For matching operations, like only for oneMatch method, 2 credits are deducted per operation.
As input, both the Resume and Job Description (JD) must be parsed in the request. - You can run unlimited searches on indexed documents without using additional credits.
3. Tracking Credit Usage
You can monitor parsing and indexing credit usage in two ways:
-
Through MyAccount:
- Go to MyAccount → Parsing Logs to see all parsed and indexed documents and the credits used.
-
Programmatically via API:
- Check ApiInfo.CreditLeft in the response of Resume Parse API calls to view remaining credits.
4. Important Notes
- Only indexed documents are searchable or matchable. Parsing alone does not allow search or match operations.
- To optimize credit usage:
- Avoid indexing duplicate documents.
- Regularly track your credit usage to prevent unexpected depletion.
For further assistance, visit the Search & Match documentation or contact .RChilli Support
Comments
0 comments
Article is closed for comments.