{"files":{"SKILL.md":"---\nname: semantic-api\ndescription: \"Semantic API skill. Use when working with Semantic for name, search.json. Covers 2 endpoints.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# Semantic API\nAPI version: 2.0.0\n\n## Auth\nApiKey api-key in query\n\n## Base URL\nhttp://api.nytimes.com/svc/semantic/v2/concept\n\n## Setup\n1. Set your API key in the appropriate header\n2. GET /search.json -- verify access\n3. Explore available endpoints below\n\n## Endpoints\n2 endpoints across 2 groups. See references/api-spec.lap for full details.\n\n### Name\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /name/{concept-type}/{specific-concept}.json |  |\n\n### Search.json\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /search.json |  |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"Get name details?\" -> GET /name/{concept-type}/{specific-concept}.json\n- \"Search search.json?\" -> GET /search.json\n- \"How to authenticate?\" -> See Auth section above\n\n## Response Tips\n- Check response schemas in references/api-spec.lap for field details\n- Paginated endpoints accept limit/offset or cursor parameters\n\n## References\n- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas\n\n> Generated from the official API spec by [LAP](https://lap.sh)\n","references/api-spec.lap":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api Semantic API\n@base http://api.nytimes.com/svc/semantic/v2/concept\n@version 2.0.0\n@auth ApiKey api-key in query\n@endpoints 2\n@toc name(1), search.json(1)\n\n@group name\n@endpoint GET /name/{concept-type}/{specific-concept}.json\n@required {concept-type: any # The type of the concept, used for Constructing a Semantic API Request by Concept Type and Specific Concept Name. The parameter is defined as a name-value pair, as in \"concept_type=[nytd_geo|nytd_per|nytd_org|nytd_des]\"., specific-concept: any # The name of the concept, used for Constructing a Semantic API Request by Concept Type and Specific Concept Name. The parameter is defined in the URI path, as the element immediately preceding \".json\" like with \"Baseball.json\"., query: any # Precedes the search term string. Used in a Search Query. Except for , Search Query will take the required parameters listed above (, , ) as an optional_parameter in addition to the query=.}\n@optional {fields: any # \"all\" or comma-separated list of specific optional fields: pages, ticker_symbol, links, taxonomy, combinations, geocodes, article_list, scope_notes, search_api_query  Optional fields are returned in result_set. They are briefly explained here:  pages: A list of topic pages associated with a specific concept. ticker_symbol: If this concept is a publicly traded company, this field contains the ticker symbol. links: A list of links from this concept to external data resources. taxonomy: For descriptor concepts, this field returns a list of taxonomic relations to other concepts. combinations: For descriptor concepts, this field returns a list of the specific meanings tis concept takes on when combined with other concepts. geocodes: For geographic concepts, the full GIS record from geonames. article_list: A list of up to 10 articles associated with this concept. scope_notes: Scope notes contains clarifications and meaning definitions that explicate the relationship between the concept and an article. search_api_query: Returns the request one would need to submit to the Article Search API to obtain a list of articles annotated with this concept.}\n@returns(200) An array of Concepts\n\n@endgroup\n\n@group search.json\n@endpoint GET /search.json\n@required {query: any # Precedes the search term string. Used in a Search Query. Except for , Search Query will take the required parameters listed above (, , ) as an optional_parameter in addition to the query=.}\n@optional {offset: any # Integer value for the index count from the first concept to the last concept, sorted alphabetically. Used in a Search Query. A Search Query will return up to 10 concepts in its results., fields: any # \"all\" or comma-separated list of specific optional fields: pages, ticker_symbol, links, taxonomy, combinations, geocodes, article_list, scope_notes, search_api_query  Optional fields are returned in result_set. They are briefly explained here:  pages: A list of topic pages associated with a specific concept. ticker_symbol: If this concept is a publicly traded company, this field contains the ticker symbol. links: A list of links from this concept to external data resources. taxonomy: For descriptor concepts, this field returns a list of taxonomic relations to other concepts. combinations: For descriptor concepts, this field returns a list of the specific meanings tis concept takes on when combined with other concepts. geocodes: For geographic concepts, the full GIS record from geonames. article_list: A list of up to 10 articles associated with this concept. scope_notes: Scope notes contains clarifications and meaning definitions that explicate the relationship between the concept and an article. search_api_query: Returns the request one would need to submit to the Article Search API to obtain a list of articles annotated with this concept.}\n@returns(200) An array of Concepts\n\n@endgroup\n\n@end\n"}}