Unlocking Possibilities: A Deep Dive into the World of ChatGPT Plugins
OpenAI sparked a revolution in the field of AI-driven communication with the launch ChatGPT Plugins. These plugins, designed for a multitude of domains including Marketing, Podcasts, Finances, SEO, News, and more, have continued to be an indispensable resource for users looking to elevate their ChatGPT experience. As we reflect on the past year, it becomes evident that these plugins have not only endured but have also significantly impacted and transformed the landscape of AI-enhanced communication.
OpenAI's commitment to empowering users is exemplified through the enduring impact and versatility of these plugins. Users across various industries have found unparalleled support in their day-to-day tasks, thanks to the specialized functionalities provided by these plugins. Whether it's crafting marketing content, generating podcast scripts, managing finances, optimizing for search engines, staying updated with the latest news, or delving into other domains, these plugins have proven to be invaluable tools.
In this article, we'll delve into the enduring impact of these ChatGPT plugins, exploring how they have shaped a new era in AI-enhanced communication. The plugins not only showcase the capabilities of ChatGPT but also highlight OpenAI's commitment to providing users with powerful and tailored AI solutions.
As part of this exploration, we'll focus on 16 ChatGPT plugins, each catering to specific user needs. The detailed API documents for these plugins, attached herewith, serve as a comprehensive guide for users looking to leverage the capabilities of ChatGPT in diverse domains. By delving into the functionalities and use cases of these plugins, users can unlock new possibilities and streamline their workflows.
As we continue to witness the evolution of AI communication, these plugins stand as a testament to the transformative potential of ChatGPT. OpenAI's foresight in developing these specialized tools has not only met the expectations of users but has also set a benchmark for the future of AI-driven applications.
The journey over the past year exemplifies the enduring relevance of ChatGPT plugins, and we look forward to further innovations that will undoubtedly shape the future of AI-enhanced communication.I hope to write about many other ChatGPT plugins in the future.
1) SEO CORE AI:
Use AI to analyze and improve the SEO of a website.A ChatGPT Plugin for Near Real-time Content Analysis & SEO.Get associated data for analyzing and comparing SEO and content from a web page by website, competition or keyword.
openapi: 3.0.0
info:
title: SEO CORE AI
description: Get associated data for analyzing and comparing SEO and content from a web page by website, competition or keyword.
version: 1.0.1
servers:
- url: https://ai.seovendor.co
paths:
/core-analysis:
get: # Change method to GET
summary: Analyze SEO or assess content for a given URL and keyword
operationId: seogpt-plugin
parameters: # Use query parameters instead of request body
- in: query
name: url
schema:
type: string
description: The URL to analyze (if it is not blocked by robots.txt). If the URL is not present, then URL analysis will not be shown.
required: false
- in: query
name: kw
schema:
type: string
description: The keyword to analyze for SERP results. If the keyword is not present, then websites that rank in Google are not shown.
required: false
responses:
'200':
description: Successful response
content:
application/json:
schema:
type: object
properties:
result:
type: string
description: Analysis result
components:
schemas:
SeoVendorResponse:
type: object
properties:
SiteResponse:
type: integer
example: 200
LoadSpeed:
type: integer
description: The time it takes to load a site.
example: 260.89ms
URL:
type: object
description: URL analysis data
properties:
URLText:
type: string
description: The text of the URL
example: "https://seovendor.co"
URLCount:
type: integer
description: The character count of the URL
example: 20
URLBASECount:
type: array
description: An array of base terms and their counts in the URL
items:
type: object
properties:
Base:
type: string
description: The base term
BaseCount:
type: integer
description: The count of the base term in the URL
URLTotalBASECount:
type: integer
description: The total count of base terms in the URL
example: 1
NoSSL:
type: string
description: The status of the non-SSL version of the website (http)
NoSSLwww:
type: string
description: The status of the non-SSL version of the website with 'www' (http)
SSL:
type: string
description: The status of the SSL version of the website (https)
SSLwww:
type: string
description: The status of the SSL version of the website with 'www' (https)
SiteAuthority:
type: integer
description: The site authority score. The score ranges from 0 to 10.
PageAuthority:
type: integer
description: The page authority score, The score ranges from 0 to 100.
keyword:
type: array
description: An array of keyword analysis data
items:
type: object
properties:
KW:
type: string
description: The keyword
Score:
type: integer
description: The score of the keyword. Higher score is more unique.
Title:
type: object
description: Title analysis data
properties:
TitleText:
type: string
description: The text of the title
example: "White Label SEO, PPC, and Web Design Reseller Platform - Sign Up for Free"
TitleCount:
type: integer
description: The character count of the title
example: 73
TitleEMTCount:
type: integer
description: The count of emphasized terms in the title
example: 1
TitleWordCount:
type: integer
description: The word count of the title
example: 14
P_TitleEMTCount:
type: integer
format: float
description: The percentage of emphasized terms in the title
example: 21
TitleBASECount:
type: array
description: An array of base terms and their counts in the title
items:
type: object
properties:
Base:
type: string
description: The base term
BaseCount:
type: integer
description: The count of the base term in the title
P_BaseCount:
type: integer
format: float
description: The percentage of the base term in the title
TitleTotalBASECount:
type: integer
description: The total count of base terms in the title
example: 3
Meta:
type: object
description: Meta description analysis data
properties:
MetaText:
type: string
description: The text of the meta description
example: "White Label services lets you rebrand our SEO/PPC/Marketing services as your own. Newest AI dashboard, AI-driven analytics, and lead generation for marketing agencies."
MetaCount:
type: integer
description: The character count of the meta description
example: 167
MetaEMTCount:
type: integer
description: The count of emphasized terms in the meta description
example: 0
MetaWordCount:
type: integer
description: The word count of the meta description
example: 25
P_MetaEMTCount:
type: integer
format: float
description: The percentage of emphasized terms in the meta description
example: 0
MetaBASECount:
type: array
description: An array of base terms and their counts in the meta description
items:
type: object
properties:
Base:
type: string
description: The base term
BaseCount:
type: integer
description: The count of the base term in the meta description
P_BaseCount:
type: integer
format: float
description: The percentage of the base term in the meta description
MetaTotalBASECount:
type: integer
description: The total count of base terms in the meta description
example: 3
Robots:
type: string
description: Robots meta tag to control search engine crawl
example: "noindex, follow"
H1:
type: array
description: An array of H1 heading analysis data
items:
type: object
properties:
H1Text:
type: string
description: The text of the H1 heading
example: "Free White Label SEO, PPC, and Website Reseller Platform"
H1Count:
type: integer
description: The character count of the H1 heading
example: 56
H1EMTCount:
type: integer
description: The count of emphasized terms in the H1 heading
example: 1
H1WordCount:
type: integer
description: The word count of the H1 heading
example: 9
P_H1EMTCount:
type: integer
format: float
description: The percentage of emphasized terms in the H1 heading
example: 33
H1BASECount:
type: array
description: An array of base terms and their counts in the H1 heading
items:
type: object
properties:
Base:
type: string
description: The base term
BaseCount:
type: integer
description: The count of the base term in the H1 heading
P_BaseCount:
type: integer
format: float
description: The percentage of the base term in the H1 heading
H1TotalBASECount:
type: integer
description: The total count of base terms in the H1 heading
example: 3
H2:
type: array
description: An array of H2 heading analysis data
items:
type: object
properties:
H2Text:
type: string
description: The text of the H2 heading
H2Count:
type: integer
description: The character count of the H2 heading
H2EMTCount:
type: integer
description: The count of emphasized terms in the H2 heading
H2WordCount:
type: integer
description: The word count of the H2 heading
P_H2EMTCount:
type: integer
format: float
description: The percentage of emphasized terms in the H2 heading
H2BASECount:
type: array
description: An array of base terms and their counts in the H2 heading
items:
type: object
properties:
Base:
type: string
description: The base term
BaseCount:
type: integer
description: The count of the base term in the H2 heading
P_BaseCount:
type: integer
format: float
description: The percentage of the base term in the H2 heading
H2TotalBASECount:
type: integer
description: The total count of base terms in the H2 heading
H3:
type: array
description: An array of H3 heading analysis data
items:
type: object
properties:
H3Text:
type: string
description: The text of the H3 heading
H3Count:
type: integer
description: The character count of the H3 heading
H3EMTCount:
type: integer
description: The count of emphasized terms in the H3 heading
H3WordCount:
type: integer
description: The word count of the H3 heading
P_H3EMTCount:
type: integer
format: float
description: The percentage of emphasized terms in the H3 heading
H3BASECount:
type: array
description: An array of base terms and their counts in the H3 heading
items:
type: object
properties:
Base:
type: string
description: The base term
BaseCount:
type: integer
description: The count of the base term in the H3 heading
P_BaseCount:
type: integer
format: float
description: The percentage of the base term in the H3 heading
H3TotalBASECount:
type: integer
description: The total count of base terms in the H3 heading
Body:
type: object
description: An object containing analysis data for the body content
properties:
BodyCount:
type: integer
description: The character count of the body content
BodyEMTCount:
type: integer
description: The count of emphasized terms in the body content
BodyWordCount:
type: integer
description: The word count of the body content
P_BodyEMTCount:
type: integer
format: float
description: The percentage of emphasized terms in the body content
Content:
type: array
description: An array of content segments in the body
items:
type: string
description: A content segment in the body
BodyBASECount:
type: array
description: An array of base terms and their counts in the body content
items:
type: object
properties:
Base:
type: string
description: The base term
BaseCount:
type: integer
description: The count of the base term in the body content
P_BaseCount:
type: integer
format: float
description: The percentage of the base term in the body content
BodyTotalBASECount:
type: integer
description: The total count of base terms in the body content
Notes:
type: string
description: Notes on the analysis based on the input
IndexedInGoogle:
type: string
description: Search Google and describes if the page is indexed.
Sitemap:
type: object
description: An object containing information about the sitemap
properties:
Result:
type: string
description: The result status of the sitemap
Info:
type: string
description: The URL of the sitemap
Robots_txt:
type: object
description: An object containing information about the robots.txt file
properties:
Result:
type: string
description: The result status of the robots.txt file
TopRankedSites:
type: object
description: Get a list of top competitor URLs to analyze or get rankings data
properties:
TopRankedSites:
type: array
description: An array of top Google ranked sites for the specified keyword
items:
type: object
properties:
link:
type: string
description: The URL of the ranked site
ranking:
type: integer
description: The ranking position of the site
self:
type: integer
description: Indicates whether the site is self-owned (1) or not (0)
2) MixerBox News:
Get latest news delivered right to you.MixerBox News provides users with the latest news, including breaking news and a wide range of news categories, such as business, finance, economics, politics, society, entertainment, fun, gossip, sports, lifestyle, technology, local, world, international, global, and military. Users who want to stay informed about current events and developments in various areas will find MixerBox News useful.
{
"openapi": "3.0.1",
"info": {
"title": "MixerBox News Plugin",
"description": "Plugin for real-time & categorized news with links and dates. Provides info on significant global events. Allow users to stay informed with what is happening around the world.",
"version": "v1"
},
"servers": [
{
"url": "https://api.mixerboxnews.com"
}
],
"paths": {
"/services?funcs=GetLatestNewsForChatGPT&mobile=1&isPlugin=true": {
"get": {
"operationId": "getLatestNews",
"summary": "Get real-time or categorized news based on user's language with links and dates.",
"description": "Users can request real-time news updates or categorized news. Each news item comes with a link and date, and users can ask for more information at the end of the content.",
"parameters": [
{
"in": "query",
"name": "isToday",
"schema": {
"type": "boolean"
},
"description": "If the content mentions a word related to 'today', then it is true, otherwise it is false."
},
{
"in": "query",
"name": "language",
"schema": {
"type": "string"
},
"description": "Determine the user locale based on their language, using the format of language code in ISO-639 format, for example, 'zh' for Chinese.",
"required": true
},
{
"in": "query",
"name": "country",
"schema": {
"type": "string"
},
"description": "Determine the user locale based on their language, using the country code in ISO-3166 format, for example, 'TW' for Taiwan.",
"required": true
},
{
"in": "query",
"name": "category",
"schema": {
"type": "string",
"enum": [
"business",
"finance",
"economics",
"politics",
"society",
"entertainment",
"fun",
"gossip",
"sports",
"lifestyle",
"technology",
"local",
"world",
"international",
"global",
"military"
]
},
"description": "If the user mentions related keyword in any languages, use the corresponding category ('business', 'finance', 'economics', 'politics', 'society', 'entertainment', 'fun', 'gossip', 'sports', 'lifestyle', 'technology', 'local', 'world', 'international', 'global', 'military') as a category parameter. If the user does not mention any specific keyword, the default value for the category parameter is an empty string."
},
{
"in": "query",
"name": "keyword",
"schema": {
"type": "string"
},
"description": "Based on the context, infer the keywords that the user wants to search for. If there are no matching keywords, default to an empty string."
}
],
"responses": {
"200": {
"description": "OK",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/LatestNewsResponse"
}
}
}
}
}
}
}
},
"components": {
"schemas": {
"LatestNewsResponse": {
"required": ["getLatestNews"],
"type": "object",
"properties": {
"getLatestNews": {
"type": "array",
"title": "Result Of Latest News List",
"description": "Result of latest news list.",
"items": {
"$ref": "#/components/schemas/NewsItem"
}
}
}
},
"NewsItem": {
"type": "object",
"properties": {
"ref": {
"type": "string",
"title": "News URL"
},
"title": {
"type": "string",
"title": "News Title"
},
"subtitle": {
"type": "string",
"title": "News Subtitle"
},
"thumbnail": {
"type": "string",
"title": "News Thumbnail"
},
"created": {
"type": "string",
"title": "News Published Time"
}
}
}
}
}
}
3) Podcast search:
This tool explores podcasts from PodcastIndex.org, a platform for decentralized audio content discovery.
openapi: 3.0.1
info:
title: Podcast search
description: This tool explores podcasts from PodcastIndex.org, a platform for decentralized audio content discovery.
version: '1.1.0' # versioning should follow the format 'major.minor.patch'
servers:
- url: https://esne.ai
paths:
/podcasts/{podcasttitle}:
get:
operationId: getPodcasts
summary: Get the list of podcasts
parameters:
- in: path
name: podcasttitle
schema:
type: string
required: true
description: The title of the podcast.
responses:
"200":
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/getPodcastsResponse'
/podcast-episodes/{podcasttitle}:
get:
operationId: getPodcastEpisodes
summary: Get the list of episodes for given podcast
parameters:
- in: path
name: podcasttitle
schema:
type: string
required: true
description: The title of the podcast.
responses:
"200":
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/getPodcastEpisodesResponse'
components:
schemas:
getPodcastsResponse:
type: object
properties:
podcasts:
type: array
items:
type: string
description: The list of podcasts.
getPodcastEpisodesResponse:
type: object
properties:
podcasts:
type: array
items:
type: string
description: The list of podcast episodes.
4) Boolio:
The easiest way to analyze global stock values.Boolio Invest is a powerful tool that allows you to delve deep into the world of stocks and equities. It provides comprehensive financial data for businesses around the globe, allowing you to conduct high-level quantitative analyses. Whether you're looking to screen or backtest various investment styles, or simply want to explore a diverse range of traditional and alternative data, this plugin is your gateway to a wealth of information.
openapi: 3.1.0
info:
title: Boolio ChatGPT plugin
version: 2023.7.1
summary: Analyze stock investments from any country, with Boolio's state-of-the-art
engine.
paths:
/api/stock/summary:
post:
summary: Summarize stock info
description: Summarize stock info of the given country and ticker
operationId: postApiStockSummary
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/StockSummaryRequest'
required: true
responses:
'200':
description: ''
content:
text/plain:
schema:
type: string
'400':
description: 'Invalid value for: body'
content:
text/plain:
schema:
type: string
'404':
description: ''
content:
text/plain:
schema:
type: string
'500':
description: ''
content:
text/plain:
schema:
type: string
/api/search/factor:
get:
summary: Search factor
description: Search for factor by keywords. If the query is an empty string,
`category` field must be set.
operationId: getApiSearchFactor
parameters:
- name: query
in: query
description: Keywords in English to search for the factor
required: true
schema:
type: string
- name: category
in: query
description: The category the factor belongs to. Should be one of the examples
when the query is empty.
required: false
schema:
type: string
examples:
Example0:
value: Scoring
Example1:
value: Value
Example2:
value: Efficiency
Example3:
value: Profitability
Example4:
value: Growth
Example5:
value: Stability
Example6:
value: Price
Example7:
value: Volume
Example8:
value: Statistics
Example9:
value: Shareholder Policy
Example10:
value: Analyst Outlook
responses:
'200':
description: ''
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/FactorDefinition'
'400':
description: 'Invalid value for: query parameter query, Invalid value for:
query parameter category'
content:
text/plain:
schema:
type: string
'404':
description: ''
content:
text/plain:
schema:
type: string
'500':
description: ''
content:
text/plain:
schema:
type: string
/api/search/sector:
get:
summary: Search industry sectors
description: Search for sector IDs by keywords.
operationId: getApiSearchSector
parameters:
- name: query
in: query
description: Keywords in English to search for the factor
required: true
schema:
type: string
responses:
'200':
description: ''
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Sector'
'400':
description: 'Invalid value for: query parameter query'
content:
text/plain:
schema:
type: string
'404':
description: ''
content:
text/plain:
schema:
type: string
'500':
description: ''
content:
text/plain:
schema:
type: string
/api/custom-index/screen:
post:
summary: Screen stocks
description: |
Search for stocks meeting the given criteria.
Note:
Before calling this endpoint, please ensure to call `/api/search/factor` first to search for the factor.
Please ensure the value is in the correct unit corresponding to the factor.
operationId: postApiCustom-indexScreen
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/ScreenerRequest'
required: true
responses:
'200':
description: ''
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/ScreenerItem'
'400':
description: 'Invalid value for: body'
content:
text/plain:
schema:
type: string
'404':
description: ''
content:
text/plain:
schema:
type: string
'500':
description: ''
content:
text/plain:
schema:
type: string
components:
schemas:
Direction:
type: string
description: The sort direction
enum:
- ASC
- DESC
FactorDefinition:
required:
- id
- name
- description
- unit
- category
type: object
properties:
id:
$ref: '#/components/schemas/FactorId'
name:
type: string
description: The name of the factor
description:
type: string
description: The meaning of the factor
unit:
type: string
description: The unit of the factor
category:
type: string
description: The category of the factor
FactorId:
type: integer
description: The unique identifier for the factor
format: int32
example: 1113
FilterCondition:
required:
- factorId
- operator
- value
- searchMode
type: object
properties:
factorId:
$ref: '#/components/schemas/FactorId'
operator:
$ref: '#/components/schemas/FilterOperator'
value:
type: number
description: The minimum threshold. If `searchMode` is `RELATIVE`, the scale
of value is percent.
format: double
searchMode:
$ref: '#/components/schemas/SearchMode'
example:
factorId: 1133
operator: '>='
value: 100.0
searchMode: Absolute
FilterOperator:
type: string
description: Operator
enum:
- '>'
- '>='
- <=
- <
GroupId:
type: integer
description: |
The unique identifier for the group or sector.
format: int32
ScreenerItem:
required:
- name
type: object
properties:
name:
type: string
symbol:
type: string
ScreenerRequest:
required:
- prompt
- region
- limit
type: object
properties:
prompt:
type: string
description: The latest chat prompt from the user
region:
type: string
description: An ISO-3166-1 alpha-2 code of the country
example: KR
sectorIds:
type: array
items:
$ref: '#/components/schemas/GroupId'
description: Sector identifiers that can be found from at `/api/sector/search`
filterRules:
type: array
items:
$ref: '#/components/schemas/FilterCondition'
description: The search criteria. Multiple conditions mean logical and (&&).
The factors should be identified by numeric ID that can be found at GET
/api/custom-index/factors
sortRules:
type: array
items:
$ref: '#/components/schemas/SortingRule'
description: The sorting criteria, which can be used to find top N items
that meets the search criteria.
limit:
type: integer
description: The maximum number of stocks in the result
format: int32
SearchMode:
type: string
description: Whether the type of value is absolute or relative. If `searchMode`
is `RELATIVE`, the scale of value is percent.
enum:
- Absolute
- Relative
Sector:
required:
- id
- name
- level
type: object
properties:
id:
$ref: '#/components/schemas/GroupId'
name:
type: string
level:
type: integer
description: The hierarchical level of the sector. The higher is the narrower.
format: int32
SortingRule:
required:
- factorId
- direction
type: object
properties:
factorId:
$ref: '#/components/schemas/FactorId'
direction:
$ref: '#/components/schemas/Direction'
example:
factorId: 1113
direction: DESC
StockSummaryRequest:
required:
- prompt
- region
- symbol
type: object
properties:
prompt:
type: string
description: The latest chat prompt from the user
region:
type: string
description: An ISO-3166-1 alpha-2 code of the country
example: JP
symbol:
type: string
description: The identifier of the stock in the corresponding region
example: AAPL
5) Tomorrow Io:
Predicting, planning, and adapting to the weather forecast.Allows you to predict, plan, and adapt to weather via contextualized insights about the forecast.
openapi: 3.0.0
info:
title: Tomorrow.io, Weather Intelligence
description: Allows you to predict, plan, and adapt to weather via contextualized insights about the forecast.
version: 1.0.0
servers:
- url: https://api.tomorrow.io
paths:
/v4/chat:
post:
operationId: handleWeatherQuestion
summary: Answer weather and climate-related questions
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
question:
type: string
description: The user's question related to weather or climate.
required:
- question
responses:
"200":
description: OK
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
answer:
type: string
description: The answer to the user's question.
id:
type: string
description: Unique identifier of question/answer.
required:
- answer
- id
default:
description: error response
content:
application/json:
schema:
type: object
properties:
code:
type: number
message:
type: string
type:
type: string
required:
- code
- message
- type
6) Open Lecture:
Discover and access the right moments in open lecture.Accepts search query objects array each with query and optional filter. Break down complex questions into sub-questions. Refine results by source, don't do this often. Split queries if ResponseTooLargeError occurs.
openapi: 3.0.2
info:
title: Open Lecture
description: Discover and access the material in open course lectures for targeted learning.
version: 1.0.1
servers:
- url: https://lorelattice.com/
paths:
/query:
post:
summary: Query
description: Accepts search query objects array each with query and optional filter. Break down complex questions into sub-questions. Refine results by source, don't do this often. Split queries if ResponseTooLargeError occurs.
operationId: query_query_post
requestBody:
content:
application/json:
schema:
$ref: "#/components/schemas/QueryRequest"
required: true
responses:
"200":
description: Successful Response
content:
application/json:
schema:
$ref: "#/components/schemas/QueryResponse"
"422":
description: Validation Error
content:
application/json:
schema:
$ref: "#/components/schemas/HTTPValidationError"
security:
- HTTPBearer: []
components:
schemas:
DocumentChunkMetadata:
title: DocumentChunkMetadata
type: object
properties:
title:
title: Lecture Title
type: string
url:
title: Url
type: string
course_url:
title: Course Url
type: string
created_at:
title: Created At
type: string
duration:
title: Duration
type: string
source_id:
title: Source ID
type: string
author:
title: Author
type: string
source:
$ref: "#/components/schemas/Source"
document_id:
title: Document Id
type: string
DocumentChunkWithScore:
title: DocumentChunkWithScore
required:
- text
- metadata
- score
type: object
properties:
id:
title: Id
type: string
text:
title: Text
type: string
metadata:
$ref: "#/components/schemas/DocumentChunkMetadata"
embedding:
title: Embedding
type: array
items:
type: number
score:
title: Score
type: number
DocumentMetadataFilter:
title: DocumentMetadataFilter
type: object
properties:
document_id:
title: Document Id
type: string
source:
$ref: "#/components/schemas/Source"
source_id:
title: Source ID
type: string
author:
title: Author
type: string
start_date:
title: Start Date
type: string
end_date:
title: End Date
type: string
HTTPValidationError:
title: HTTPValidationError
type: object
properties:
detail:
title: Detail
type: array
items:
$ref: "#/components/schemas/ValidationError"
Query:
title: Query
required:
- query
type: object
properties:
query:
title: Query
type: string
filter:
$ref: "#/components/schemas/DocumentMetadataFilter"
top_k:
title: Top K
type: integer
default: 3
QueryRequest:
title: QueryRequest
required:
- queries
type: object
properties:
queries:
title: Queries
type: array
items:
$ref: "#/components/schemas/Query"
QueryResponse:
title: QueryResponse
required:
- results
type: object
properties:
results:
title: Results
type: array
items:
$ref: "#/components/schemas/QueryResult"
QueryResult:
title: QueryResult
required:
- query
- results
type: object
properties:
query:
title: Query
type: string
results:
title: Results
type: array
items:
$ref: "#/components/schemas/DocumentChunkWithScore"
Source:
title: Source
enum:
- video
- pdf
type: string
description: An enumeration.
ValidationError:
title: ValidationError
required:
- loc
- msg
- type
type: object
properties:
loc:
title: Location
type: array
items:
anyOf:
- type: string
- type: integer
msg:
title: Message
type: string
type:
title: Error Type
type: string
securitySchemes:
HTTPBearer:
type: http
scheme: bearer
7) Abridged Due Diligence:
Accepts search query objects array. Break down complex questions into sub-questions. Add a filter object to the query with a ticker attribute to get relevant results. Leave a link to allow the user to discover more details, in the format: abridgeddd.com/details/{acc_no}.
openapi: 3.0.2
info:
title: Abridged Due Diligence
description: A retrieval API for querying and filtering SEC filings
version: 1.0.0
servers:
- url: https://vector-api.fly.dev
paths:
/query:
post:
summary: Query
description: "Accepts search query objects array each with query and required ticker filter. Break down complex questions into sub-questions."
operationId: query_query_post
requestBody:
content:
application/json:
schema:
$ref: "#/components/schemas/QueryRequest"
required: true
responses:
"200":
description: Successful Response
content:
application/json:
schema:
$ref: "#/components/schemas/QueryResponse"
"422":
description: Validation Error
content:
application/json:
schema:
$ref: "#/components/schemas/HTTPValidationError"
components:
schemas:
DocumentChunkMetadata:
title: DocumentChunkMetadata
type: object
properties:
created_at:
title: Created At
type: string
ticker:
title: Ticker
type: string
acc_no:
title: Accession Number
type: string
document_id:
title: Document Id
type: string
DocumentChunkWithScore:
title: DocumentChunkWithScore
required:
- text
- metadata
- score
type: object
properties:
id:
title: Id
type: string
text:
title: Text
type: string
metadata:
$ref: "#/components/schemas/DocumentChunkMetadata"
embedding:
title: Embedding
type: array
items:
type: number
score:
title: Score
type: number
DocumentMetadataFilter:
title: DocumentMetadataFilter
type: object
properties:
created_at:
title: Created At
type: string
ticker:
title: Ticker
type: string
acc_no:
title: Accession Number
type: string
document_id:
title: Document Id
type: string
HTTPValidationError:
title: HTTPValidationError
type: object
properties:
detail:
title: Detail
type: array
items:
$ref: "#/components/schemas/ValidationError"
Query:
title: Query
required:
- query
- filter
type: object
properties:
query:
title: Query
type: string
filter:
$ref: "#/components/schemas/DocumentMetadataFilter"
type: object
top_k:
title: Top K
type: integer
default: 5
QueryRequest:
title: QueryRequest
required:
- queries
type: object
properties:
queries:
title: Queries
type: array
items:
$ref: "#/components/schemas/Query"
QueryResponse:
title: QueryResponse
required:
- results
type: object
properties:
results:
title: Results
type: array
items:
$ref: "#/components/schemas/QueryResult"
QueryResult:
title: QueryResult
required:
- query
- results
type: object
properties:
query:
title: Query
type: string
results:
title: Results
type: array
items:
$ref: "#/components/schemas/DocumentChunkWithScore"
Source:
title: Source
enum:
- email
- file
- chat
type: string
description: An enumeration.
ValidationError:
title: ValidationError
required:
- loc
- msg
- type
type: object
properties:
loc:
title: Location
type: array
items:
anyOf:
- type: string
- type: integer
msg:
title: Message
type: string
type:
title: Error Type
type: string
领英推荐
8) Local by GoodCall:
Discover and support restaurants, shops & services near you. A ChatGPT extension giving consumers access to information surrounding businesses using the Yelp, Google Maps, and GoodCall apis.
openapi: 3.0.1
info:
title: Local
description: A ChatGPT extension giving consumers access to information
surrounding businesses using the Yelp, Google Maps, and GoodCall apis.
version: v1
servers:
- url: https://local.goodcall.ai
components:
schemas:
-well-known-ai-plugin-json-getResponse:
type: object
properties: {}
businesses-search-getResponse:
type: object
properties:
businesses:
type: array
items:
type: object
properties:
business_url:
type: string
display_address:
type: array
items:
type: string
name:
type: string
display_phone:
type: string
required:
- business_url
- display_address
- name
- display_phone
required:
- businesses
categories-getResponse:
type: object
properties:
categories:
type: array
items:
type: object
properties:
alias:
type: string
description: Category alias
title:
type: string
description: Category title
parent_aliases:
type: array
items:
type: string
description: List of aliases of parent categories
country_whitelist:
type: array
items:
type: string
description: List of country codes this category is available in
country_blacklist:
type: array
items:
type: string
description: List of country codes this category is not available in
required:
- alias
- title
- parent_aliases
- country_whitelist
- country_blacklist
required:
- categories
logo-png-getResponse:
type: string
openapi-yaml-getResponse:
type: string
parameters: {}
paths:
/.well-known/ai-plugin.json:
get:
operationId: -well-known-ai-plugin-json
summary: The plugin manifest used by ChatGPT
x-google-backend:
address: https://local--well-known-ai-plugin-json-get-6dtsqvpbyq-uc.a.run.app
responses:
"200":
description: The manifest file.
content:
application/json:
schema:
$ref: "#/components/schemas/-well-known-ai-plugin-json-getResponse"
/businesses/search:
get:
operationId: businesses-search
summary: Search for businesses by keyword, category, location, price level, etc.
x-google-backend:
address: https://local-businesses-search-get-6dtsqvpbyq-uc.a.run.app
parameters:
- schema:
type: string
description: Search term, e.g. "food" or "restaurants". The term may also be the
business's name, such as "Starbucks". If term is not included the
endpoint will default to searching across businesses from a small
number of popular categories.
required: false
name: term
in: query
- schema:
type: string
description: 'Required if either latitude or longitude is not provided. This
string indicates the geographic area to be used when searching for
businesses. Examples: "New York City", "NYC", "350 5th Ave, New
York, NY 10118". Businesses returned in the response may not be
strictly within the specified location.'
required: false
name: location
in: query
- schema:
type: number
default: 3
description: Number of results to return. Always default to 3 unless specified
with an exact amount by the user.
required: false
name: limit
in: query
- schema:
type: number
description: Offset the list of returned results by this amount.
required: false
name: offset
in: query
- schema:
type: string
description: Required, if location is not provided. Latitude of the location to
search from. If latitude is provided, longitude is required too.
required: false
name: latitude
in: query
- schema:
type: string
description: Required if location is not provided. Longitude of the location to
search from. If longitude is provided, latitude is required too.
required: false
name: longitude
in: query
- schema:
type: string
description: A suggested search radius in meters. This field is used as a
suggestion to the search. The actual search radius may be lower
than the suggested radius in dense urban areas, and higher in
regions of less business density. If the specified value is too
large, a AREA_TOO_LARGE error may be returned. The max value is
40,000 meters (about 25 miles).
required: false
name: radius
in: query
- schema:
type: string
description: >-
Categories to filter the search results with. See the list of
supported categories. The category filter can be a list of comma
delimited categories.
e.g., "bars,french" will filter by Bars OR French.
The category alias should be used (e.g. "discgolf", not "Disc Golf").
required: false
name: categories
in: query
- schema:
type: string
description: Locale code in the format of {language code}_{country code}. See
the list of supported locales.
required: false
name: locale
in: query
- schema:
type: string
description: >-
Pricing levels to filter the search result with: 1 = $, 2 = $, 3
= $$, 4 = $$. The price filter can be a list of comma delimited
pricing levels.
e.g., "1, 2, 3" will filter the results to show the ones that are $, $, or $$.
required: false
name: price
in: query
- schema:
type: string
description: When set to true, only return the businesses that are open now.
Notice that open_at and open_now cannot be used together.
required: false
name: open_now
in: query
- schema:
type: string
description: A string representing the time in the timezone of the search
location, formatted in ISO format. Value must be greater than two
weeks ago. If specified, it will return businesses open at the
given time. Notice that open_at and open_now cannot be used
together.
required: false
name: open_at
in: query
- schema:
type: string
description: >-
Suggestion to the search algorithm that the results be sorted by
one of the these modes: best_match, rating, review_count or
distance. The default is best_match. Note that specifying the
sort_by is a suggestion (not strictly enforced) to Yelp's search,
which considers multiple input parameters to return the most
relevant results.
e.g., the rating sort is not strictly sorted by the rating value, but by an adjusted rating value that takes into account the number of ratings,
similar to a Bayesian average. This is to prevent skewing results to businesses with a single review.
required: false
name: sort_by
in: query
- schema:
type: string
description: Determines the platform for mobile_link
required: false
name: device_platform
in: query
- schema:
type: string
description: The date for the reservation, format is YYYY-mm-dd
required: false
name: reservation_date
in: query
- schema:
type: string
description: The time of the requested reservation, format is HH:MM. Required if
reservation_date is defined.
required: false
name: reservation_time
in: query
- schema:
type: number
description: How many people are attending the reservation. Required if
reservation_date and reservation_time are defined.
required: false
name: reservation_covers
in: query
- schema:
type: boolean
description: Whether to filter out results that don't have openings matching the
params
required: false
name: matches_party_size_param
in: query
responses:
"200":
description: This endpoint returns up to 1000 businesses with some basic
information based on the provided search criteria.
content:
application/json:
schema:
$ref: "#/components/schemas/businesses-search-getResponse"
"400":
description: The user passed in invalid parameters.
content:
application/json:
schema:
allOf:
- $ref: "#/components/schemas/businesses-search-getResponse"
- properties:
error:
type: string
required:
- error
"500":
description: There was an error thrown internally and the support team has
already been notified. We apologize for the inconvenience.
content:
application/json:
schema:
allOf:
- $ref: "#/components/schemas/businesses-search-getResponse"
- properties:
error:
type: string
required:
- error
/categories:
get:
operationId: categories
summary: Get all Yelp business categories across all locales.
x-google-backend:
address: https://local-categories-get-6dtsqvpbyq-uc.a.run.app
parameters:
- schema:
type: string
description: Specify the locale to filter the categories returned to only those
available in that locale, and to translate the names of the
categories appropriately. See the list of supported locales. If
not included, all categories across all locales will be returned
and the category names will be in English.
required: false
name: locale
in: query
responses:
"200":
description: This endpoint returns all Yelp business categories across all
locales by default. Include the "locale" parameter to filter to only
those categories available for a particular locale, and
translate/localize the names of those categories.
content:
application/json:
schema:
$ref: "#/components/schemas/categories-getResponse"
/logo.png:
get:
operationId: logo-png
summary: The Logo for the plugin.
x-google-backend:
address: https://local-logo-png-get-6dtsqvpbyq-uc.a.run.app
responses:
"200":
description: The image file.
content:
application/json:
schema:
$ref: "#/components/schemas/logo-png-getResponse"
/openapi.yaml:
get:
operationId: openapi-yaml
summary: The OpenAPI specification for the plugin.
x-google-backend:
address: https://local-openapi-yaml-get-6dtsqvpbyq-uc.a.run.app
responses:
"200":
description: The manifest file.
content:
application/json:
schema:
$ref: "#/components/schemas/openapi-yaml-getResponse"
9) Currency Converter:
Convert currencies based on real-time rates. Include the following words in your prompt - 'convert', 'amount', 'from' and 'to'.
openapi: 3.0.1
info:
title: Currency Converter
description: Convert currencies based on real-time rates!
version: 'v2'
servers:
- url: https://currency.orrenprunckun.com
paths:
/:
get:
operationId: convertCurrency
summary: Convert currency from one to another
parameters:
- name: from
in: query
description: The source currency code
required: true
schema:
type: string
- name: to
in: query
description: The target currency code
required: true
schema:
type: string
- name: amount
in: query
description: The amount to be converted
required: true
schema:
type: number
- name: date
in: query
description: The date for historical exchange rate (optional)
required: false
schema:
type: string
format: date
responses:
"200":
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/convertCurrencyResponse'
components:
schemas:
convertCurrencyResponse:
type: object
properties:
from:
type: string
description: The source currency code
to:
type: string
description: The target currency code
amount:
type: number
description: The amount to be converted
converted_amount:
type: number
description: The converted amount
10) CreditYelp:
Access various financial calculators and get accurate figures for personal loans and credit card payoff plans. The outputs contain repayment schedules with detailed numbers and tables.
openapi: 3.0.1
info:
version: v0
title: Open AI CreditYelp Calculator API
servers:
- url: https://www.credityelp.com/openai/calulator
tags:
- name: open-ai-calculator-endpoint
description: Open AI Calculator Endpoint. Query for repayment information.
paths:
/personalloans:
get:
tags:
- open-ai-calculator-endpoint
summary: Calculate and illustrate the repayment schedule for personal loans.
operationId: personalloansGET
parameters:
- name: money
in: query
description: The total amount of the user’s existing loan and the amount user plans to borrow.
required: true
schema:
type: string
- name: rate
in: query
description: Loan interest rate.
required: false
schema:
type: string
- name: term
in: query
description: The total number of periods that the user needs to repay the loan. Month as the unit.
required: false
schema:
type: integer
- name: creditscore
in: query
description: User's credit score.
required: false
schema:
type: string
responses:
'200':
description: Calculation Result
content:
application/json:
schema:
$ref: '#/components/schemas/PersonalloansResponse'
'503':
description: One or more services are unavailable
'400':
description: The requested scope does not meet the requirements
deprecated: false
/creditcardloans:
get:
tags:
- open-ai-calculator-endpoint
summary: Calculate and illustrate figures and repayment plans to pay off the credit card balance.
operationId: creditCardloansGET
parameters:
- name: balance
in: query
description: The total outstanding amount owed, including purchases, fees, and interest charges.
required: true
schema:
type: string
- name: rate
in: query
description: The interest rate that the credit card issuer charges on the outstanding balance.
required: false
schema:
type: string
- name: monthly_payment
in: query
description: The fixed amount that needs to be repaid each month during a given repayment period.
required: false
schema:
type: string
- name: term
in: query
description: The total number of periods the user wishes to pay off the outstanding credit card balance. Month as the unit.
required: false
schema:
type: integer
responses:
'200':
description: Calculate Credit Card loan repayment Result
content:
application/json:
schema:
$ref: '#/components/schemas/CreditCardloansResponse'
'503':
description: One or more services are unavailable
'400':
description: The requested scope does not meet the requirements
deprecated: false
components:
schemas:
PayInfoResult:
type: object
properties:
monthly_payment:
type: double
description: Monthly Payment
loan_amount:
type: double
description: Loan Amount
total_interest_paid:
type: double
description: Total interest paid
total_amount_paid:
type: double
description: Total amount paid
description: Monthly repayment information
title: Repayment Amount
CreditCardPayInfoResult:
type: object
properties:
monthly_payment:
type: double
description: Monthly Payment
credit_card_balance:
type: double
description: Credit Card Balance
interest_rate:
type: double
description: Interest Rate
months_to_payoff:
type: integer
description: Months To Payoff
total_interest_paid:
type: double
description: Total interest paid
total_amount_paid:
type: double
description: Total amount paid
description: Monthly repayment information
title: Repayment Amount
MonthPaymentInfo:
type: object
properties:
month:
type: integer
description: Specific month number of the amortization schedule
beginning_balance:
type: double
description: Starting balance amount of the amortization schedule for each payment period
interest:
type: double
description: Interest amount paid for each period on the amortization schedule
principle:
type: double
description: Principle amount paid for each period on the amortization schedule
ending_balance:
type: double
description: Ending balance amount of the amortization schedule for each payment period
title: Monthly Payment Info
description: Detailed information about the monthly payment
Result:
type: object
properties:
theme:
type: string
description: Result of this repayment calculation
paymentinfo:
type: object
description: Repayment information
items:
$ref: '#/components/schemas/PayInfoResult'
monthpaymentinfolist:
type: string
description: Detailed amortization schedule table. Return up to 30 items.
title: Calculation Result
CreditsCoreRate:
type: object
properties:
creditscore:
type: string
description: Range of the credit score
creditscore_rate:
type: string
description: Interest rate under specific credit score range
title: Rate and Score
description: Connection between interest rate and credit score
PersonalloansResponse:
type: object
properties:
Describe:
type: string
description: Main content of the answer
paymentresultlist:
type: array
items:
$ref: '#/components/schemas/Result'
Summarize:
type: string
description: Summary of answers
url:
type: string
description: Calculate your personal loan payments accurately and quickly with the personal loan calculator
description: Repayment information
title: Personal Loans Response
CreditCardloansResponse:
type: object
properties:
describe:
type: string
description: Main content of the answer
creditcardloansresult:
type: object
items:
$ref: '#/components/schemas/CreditCardPayInfoResult'
Summarize:
type: string
description: Summary of answers
recommend:
type: string
description: Recommendation of answers
url:
type: string
description: Accurately and quickly calculate your credit card loan payments with the Credit Card Loan Calculator
description: Repayment information
title: Credit Card Loans Response
11) ImageSearch:
Find and display image from unsplash. Find images and display the images with titles. Display author name and Unsplash name like this: Photo by author_name with author_website link on Unsplash with unsplash_website link. Display customize image link like this: [Customize your image using AI](customize_image_url)
openapi: 3.0.1
info:
title: ImageSearch ChatGPT Plugin
description: A plugin that connects to the Unsplash API to find and display images based on user's query.
version: 'v1'
servers:
- url: https://imgser.aigenprompt.com
paths:
/image:
get:
operationId: fetchImage
summary: Get images based on the search query
parameters:
- name: query
in: query
description: The search term to find images for
required: true
schema:
type: string
responses:
"200":
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/fetchImageResponse'
"400":
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/errorResponse'
components:
schemas:
fetchImageResponse:
related_title:
type: string
description: related title
related_url:
type: string
format: uri
description: related url
images:
type: array
items:
type: object
properties:
title:
type: string
description: The title of the image
url:
type: string
format: uri
description: The URL of the image
download_url:
type: string
format: uri
description: The URL to download the raw image
track_url:
type: string
format: uri
description: The URL to track download count after downloading the image
author_name:
type: string
description: Author name of the image
author_website:
type: string
format: uri
description: Author's website
unsplash_website:
type: string
format: uri
description: Unsplash's website
errorResponse:
type: object
properties:
error:
type: string
description: An error message describing the issue
12) Xpapers:
Find real academic papers on arXiv. This plugin allows you to search for academic papers in the arXiv database. You can use atomic conditions and boolean assembly in your search queries. Always consider using atomic conditions to refine your search. Each article is divided up into a number of fields that can individually be searched. Here are the field prefixes you can use in your search queries: 'ti' for Title, 'au' for Author, 'abs' for Abstract, 'co' for Comment, 'jr' for Journal Reference, 'cat' for Subject Category, 'rn' for Report Number, 'id' for Id (use id_list instead), 'all' for all of the above. You can also use boolean operators like AND, OR, ANDNOT in your queries. For example, 'au:del_maestro+AND+ti:checkerboard' will return papers by the author Del Maestro with 'checkerboard' in the title. You can also group your queries using parentheses and double quotes. For example, 'au:del_maestro+AND+ti:%22quantum+criticality%22' will return papers by the author Del Maestro with 'quantum criticality' in the title. You can also use abbreviations for arXiv subject categories in your queries, like 'stat.AP' for Statistics - Applications, 'cs.AI' for Computer Science - Artificial Intelligence, and so on. Remember, the more specific your search query, the more accurate your results will be. Consider using atomic conditions to refine your search.
openapi: 3.0.1
info:
title: Academic Plugin
description: >
A plugin that allows the user to search academic papers using ChatGPT. It provides endpoints for searching papers, searching papers with PDF links, searching papers by id and filter the publish date. This plugin allows you to search for academic papers in the arXiv database. You can use atomic conditions and boolean assembly in your search queries. You can use atomic conditions and boolean assembly in your search queries. Always consider using atomic conditions to refine your search. Each article is divided up into a number of fields that can individually be searched. Here are the field prefixes you can use in your search queries: 'ti' for Title, 'au' for Author, 'abs' for Abstract, 'co' for Comment, 'jr' for Journal Reference, 'cat' for Subject Category, 'rn' for Report Number, 'id' for Id (use route /search/id instead), 'all' for all of the above. You can also use boolean operators like AND, OR, ANDNOT in your queries. For example, 'au:del_maestro+AND+ti:checkerboard' will return papers by the author Del Maestro with 'checkerboard' in the title. You can also group your queries using parentheses and double quotes. For example, 'au:del_maestro+AND+ti:%22quantum+criticality%22' will return papers by the author Del Maestro with 'quantum criticality' in the title. You can also use abbreviations for arXiv subject categories in your queries, like 'stat.AP' for Statistics - Applications, 'cs.AI' for Computer Science - Artificial Intelligence, and so on.
For the search query, you can use atomic conditions and boolean assembly. Here are some examples:
- Atomic conditions: `condition("au", "Balents Leon") → "au:\"Balents Leon\""`
- Boolean assembly: `and(cond1, cond2) → "$(cond1) AND $(cond2)"`
You can also use the following prefixes in your queries:
- ti: Title
- au: Author
- abs: Abstract
- co: Comment
- jr: Journal Reference
- cat: Subject Category
- rn: Report Number
- id: Id (use id_list instead)
- all: All of the above
version: 'v2'
servers:
- url: https://xapi.lihaorui.com
paths:
/legal:
get:
summary: Get legal, contact and donate information
responses:
'200':
description: A text containing legal, contact and donate information
content:
text/plain:
schema:
type: string
/search:
post:
operationId: search_papers
summary: Search for academic papers
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/SearchRequest'
responses:
"200":
description: OK
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Paper'
"500":
description: Internal Server Error
/search/pdf:
post:
operationId: search_papers_with_pdf
summary: Search for academic papers with PDF links
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/SearchRequest'
responses:
"200":
description: OK
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Paper'
"500":
description: Internal Server Error
/search/id:
post:
operationId: search_papers_by_id
summary: Search for academic papers by id
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/SearchByIdRequest'
responses:
"200":
description: OK
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Paper'
"500":
description: Internal Server Error
/search/date:
post:
operationId: search_papers_by_date
summary: Search for academic papers by date
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
query:
type: string
description: >
The search query. Use atomic conditions and boolean assembly to refine your search.
Each article is divided up into a number of fields that can individually be searched.
Here are the field prefixes you can use in your search queries: 'ti' for Title, 'au' for Author,
'abs' for Abstract, 'co' for Comment, 'jr' for Journal Reference, 'cat' for Subject Category,
'rn' for Report Number, 'id' for Id (use id_list instead), 'all' for all of the above.
You can also use boolean operators like AND, OR, ANDNOT in your queries.
For example, 'au:del_maestro+AND+ti:checkerboard' will return papers by the author Del Maestro
with 'checkerboard' in the title. You can also group your queries using parentheses and double quotes.
For example, 'au:del_maestro+AND+ti:%22quantum+criticality%22' will return papers by the author Del Maestro
with 'quantum criticality' in the title.
max_results:
type: integer
description: The maximum number of search results to return.
start_date:
type: string
format: date
description: The start date of the search range in 'YYYY-MM-DD' format.
end_date:
type: string
format: date
description: The end date of the search range in 'YYYY-MM-DD' format.
required:
- query
- max_results
- start_date
- end_date
responses:
"200":
description: OK
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Paper'
"400":
description: Bad Request
content:
application/json:
schema:
type: object
properties:
error:
type: string
message:
type: string
"500":
description: Internal Server Error
content:
application/json:
schema:
type: object
properties:
error:
type: string
message:
type: string
components:
schemas:
SearchRequest:
type: object
required:
- query
- max_results
properties:
query:
type: string
description: >
The search query. Use atomic conditions and boolean assembly to refine your search.
Each article is divided up into a number of fields that can individually be searched.
Here are the field prefixes you can use in your search queries: 'ti' for Title, 'au' for Author,
'abs' for Abstract, 'co' for Comment, 'jr' for Journal Reference, 'cat' for Subject Category,
'rn' for Report Number, 'id' for Id (use id_list instead), 'all' for all of the above.
You can also use boolean operators like AND, OR, ANDNOT in your queries.
For example, 'au:del_maestro+AND+ti:checkerboard' will return papers by the author Del Maestro
with 'checkerboard' in the title. You can also group your queries using parentheses and double quotes.
For example, 'au:del_maestro+AND+ti:%22quantum+criticality%22' will return papers by the author Del Maestro
with 'quantum criticality' in the title.
max_results:
type: integer
description: The maximum number of search results to return. Should not bigger than 50.
SearchByIdRequest:
type: object
required:
- id_list
- max_results
properties:
id_list:
type: array
items:
type: string
description: The list of ids to search for.
max_results:
type: integer
description: The maximum number of search results to return.
Paper:
type: object
properties:
entry_id:
type: string
updated:
type: string
published:
type: string
title:
type: string
authors:
type: array
items:
type: string
summary:
type: string
comment:
type: string
journal_ref:
type: string
doi:
type: string
primary_category:
type: string
categories:
type: array
items:
type: string
links:
type: array
items:
type: string
pdf_url:
type: string
13) Tic Tac Toe:
Tic Tac Toe in chatgpt. The API endpoint is POST https://api.ludum.dev/v1/tictactoe. The API is designed for a turn-based game where users submit their move on a board with size depending on the chosen board size (9 for 3x3, 16 for 4x4, 25 for 5x5, or 36 for 6x6), and receive an updated board reflecting the AI's response move. The game can start with the AI submitting a board of all zeros or a missing board, or the player making their first move. Each player's move on the board is represented in the board array as '1' for 'X' and '2' for 'O'. For instance, if a player places an 'X' in the top left corner, the first element of the array becomes '1', or if an 'O' is placed in the center, the corresponding element in the array becomes '2'. The API response includes a 'boardDisplay' property for a visual representation of the board, but be aware that 'boardDisplay' numbering runs from 1 to n, where n is the total number of cells in the board, contrasting with the board array's 0 to n-1 indexing.
openapi: 3.0.0
info:
title: Tic Tac Toe API
description: |
An API for playing Tic Tac Toe.
The game board is represented as a single array, and the API allows users to submit the board with their move reflected in it, and receive the AI's response move reflected in the board.
version: 1.1.0
servers:
- url: https://api.ludum.dev/v1
paths:
/tictactoe:
post:
operationId: Play a move in the Tic Tac Toe game
summary: |
The API allows users to submit the board with their move reflected in it, and receive the AI's response move reflected in the board.
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
board:
type: array
items:
type: integer
description: |
The current state of the board as a single array. The array size depends on the size of the board (boardSize^2).
When the AI starts the board is submited with zeros or might be missing.
When the player starts the board is submited with the player's first move.
When the player places an X or O in a position, the value of that position in the array is set to the player's number (1 for X or 2 for O).
For example, if the player places an X in the top left corner, the value of the first element in the array is set to 1.
If the player places an O in the center, the value of the element at the center of the array is set to 2.
You can use the boardDisplay property in the response to display the board visually.
Keep note that the boardDisplay is numbered from 1 to n, where n is the total number of cells in the board, while the board array is numbered from 0 to n-1.
example: [0, 0, 0, 1, 0, 0, 0, 0, 0]
difficulty:
type: integer
description: |
The difficulty level of the AI.
Possible values are 1, 2, 3.
The higher the difficulty level, the smarter the AI.
The default difficulty level is 3.
default: 3
example: 3
boardSize:
type: integer
description: |
The size of the board.
Possible values are 3, 4, 5, 6.
The default size is 3.
default: 3
example: 3
responses:
'200':
description: Successful operation
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
description: A boolean value indicating if the move was successful.
example: true
message:
type: string
description: A text description of the move made by the player.
example: "Player 2 placed O in position 0."
board:
type: array
items:
type: integer
description: The updated game board as an array.
example: [2, 0, 0, 1, 0, 0, 0, 0, 0]
boardSize:
type: integer
description: The size of the board.
example: 3
boardDisplay:
type: string
description: The visual representation of the board as a string.
example: " O | 2 | 3 \n --------- \n X | 5 | 6 \n --------- \n 7 | 8 | 9 "
gameStatus:
type: string
description: "The current game status. Possible values include: ongoing, player1_wins, player2_wins, draw."
example: ongoing
nextPlayer:
type: integer
description: The next player to make a move (1 for X or 2 for O or -1 for Game Over).
example: 1
'400':
description: Invalid request
content:
text/plain:
schema:
type: string
description: A text with the error.
example: It's not the submitted player's turn. Please submit the correct player's move.
'404':
description: Page not found
content:
text/plain:
schema:
type: string
description: A text with the error.
example: 404 page not found
default:
description: Unexpected error
14) ChatSpot:
Get access to marketing/sales data including company research and keywords. This plugin helps users interact with their HubSpot CRM and many other SAAS tools. It can provide information on domains, companies, people, deals, tickets, and more. It can also perform actions like creating new contacts, deals, tickets, and more.
openapi: 3.0.1
info:
title: ChatSpot
description: A plugin for an AI assistant called ChatSpot that helps users interact with their HubSpot CRM and many other SAAS tools.
version: 'v1'
servers:
- url: https://do2.chatspot.ai/plugin
paths:
/chat:
post:
operationId: chat
summary: Send a message to ChatSpot
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/chatRequest'
responses:
"200":
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/chatResponse'
components:
schemas:
chatRequest:
type: object
required:
- message
properties:
message:
type: string
description: The entire message sent by the user when invoking this plugin
required: true
chatResponse:
type: object
properties:
response:
type: string
description: The text component of a ChatSpot response
data_table:
type: array
items:
type: array
items: {}
description: A two-dimensional array representing the data table component of a ChatSpot response
15) Klook:
Find the best experiences, tours, hotels and transport options. When user asks travel related questions or mentions a destination for their trips, the model can understand user's requirements and then help them book tours, book activities, book attraction tickets, book hotel rooms, book flight tickets, rent cars, reserve airport transfer service, or provide ideas about destinations.
openapi: 3.0.1
info:
title: Klook Travel Assistant Plugin
description: A plugin that assists users in planning their travel, helping them find hotels, activities, flights, trains, car rentals, and other travel products.
version: v1
servers:
- url: https://www.klook.com
paths:
/v1/gptpluginsrv/public/search:
get:
operationId: search
summary: Search for activities, hotels, flights, trains, car rentals, and other travel products
parameters:
- in: query
name: destination
schema:
type: string
required: true
description: The destination of the travel where the user wants to go
- in: query
name: departure
schema:
type: string
required: false
description: The departure of the travel where the user is from
- in: query
name: keyword
schema:
type: string
required: true
description: The keyword for the travel activity, hotel, flight, etc., that the user wants to search
- in: query
name: category
schema:
type: string
enum:
- "Things to do"
- "Attractions"
- "Theme parks"
# ... (other categories)
- "buses"
- "other"
required: true
description: The category of the travel product
- in: query
name: from_time
schema:
type: string
required: false
description: The start time of the travel (format: YYYY-MM-DD)
- in: query
name: end_time
schema:
type: string
required: false
description: The end time of the travel (format: YYYY-MM-DD)
- in: query
name: currency
schema:
type: string
required: true
description: The currency based on the user's location or input language
- in: query
name: original_input
schema:
type: string
required: true
description: The original input of the user
responses:
"200":
description: Search result
content:
application/json:
schema:
type: object
properties:
results:
type: array
items:
type: object
properties:
title:
type: string
url:
type: string
photo_url:
type: string
description: Photo to be displayed in the chat
price:
type: string
description: The selling price of the product
city_name:
type: string
category:
type: string
description: Category of the product
rating:
type: string
description: The rating of the product
IMPORTANT_INFORMATION_FOR_ASSISTANT:
type: string
16) Magnetis:
Magnetis is a digital wealth manager. Provides information and portfolio data for users and clients. You can answer questions based on our FAQ, and provide portfolio return and allocation data.
openapi: 3.1.0
info:
title: Magnetis API
version: 1.0.0
description: |
Get updated information on Magnetis portfolios including investment returns and allocations.
You can also ask general questions about wealth management and Magnetis.
servers:
- url: https://mag-gpt-nextjs.vercel.app/api
paths:
/faq:
post:
description: |
Provide context for frequently asked questions about Magnetis or any of its products such as TECB11.
The API will return the most relevant answer to the user's question. In Portuguese only.
summary: FAQ
operationId: getFAQAnswer
requestBody:
content:
application/json:
schema:
type: object
properties:
prompt:
type: string
description: The user's question or prompt. Must be in Portuguese, please translate if needed.
required:
- prompt
required: true
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
answer:
type: string
description: The relevant information to answer the user's question.
link:
type: string
description: External link for the user to find additional information. Always include in the response.
required:
- answer
'400':
description: Bad Request - Error fetching the closest answer to the question.
content:
application/json:
schema:
type: object
properties:
message:
type: string
servers:
- url: https://mag-gpt-nextjs.vercel.app/api
/portfolios/allocations:
get:
description: |
Provides the current portfolio allocation for all Magnetis portfolios.
Present the results in a table format whenever possible.
summary: Portfolio Allocation Data
operationId: getPortfolioAllocations
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
allocations:
type: array
items:
type: object
properties:
segment:
type: string
description: The client segment, typically either Infinity or Advisor/Digital.
riskLevel:
type: string
description: The risk level for the portfolio.
referenceDate:
type: string
format: date
description: The reference date of the allocation.
allocation:
type: array
items:
type: object
properties:
assetClass:
type: string
description: The asset class of the allocation.
weight:
type: number
description: The percentage of the portfolio allocated to the asset class.
required:
- assetClass
- weight
link:
type: string
description: External link for the user to find additional information. Please include in the response.
required:
- allocations
- link
'400':
description: Bad Request - Error fetching portfolio returns
content:
application/json:
schema:
type: object
properties:
message:
type: string
'401':
description: Unauthorized - Authentication token not provided
content:
application/json:
schema:
type: object
properties:
message:
type: string
'403':
description: Forbidden - Invalid authentication token
content:
application/json:
schema:
type: object
properties:
message:
type: string
servers:
- url: https://mag-gpt-nextjs.vercel.app/api
/portfolios/returns:
get:
description: |
Returns for Magnetis portfolios and benchmarks on a standard period like every year, YTD, last 12/24/36 months.
For other periods, use /portfolios/prices to fetch prices and calculate returns. Display in table format.
summary: Portfolio Returns Data
operationId: getPortfolioReturns
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
returns:
type: array
items:
type: object
properties:
category:
type: string
description: The category for the asset, typically either Portfolio, Fund, or Benchmark.
name:
type: string
description: The name used to identify the asset.
segment:
type: string
description: The client segment for the portfolio, typically either Infinity or Advisor/Digital.
not applicable for Funds or Benchmarks.
riskLevel:
type: string
description: The risk level of the portfolio.
not applicable for Funds or Benchmarks.
referenceDate:
type: string
format: date
description: The reference date of the returns data.
returns:
type: array
items:
type: object
properties:
period:
type: string
description: The period for the return.
percentageChange:
type: number
description: The percentage change of the portfolio during the period.
required:
- period
- percentageChange
link:
type: string
description: External link for the user to find additional information. Please include in the response.
required:
- returns
- link
'400':
description: Bad Request - Error fetching portfolio returns
content:
application/json:
schema:
type: object
properties:
message:
type: string
'401':
description: Unauthorized - Authentication token not provided
content:
application/json:
schema:
type: object
properties:
message:
type: string
'403':
description: Forbidden - Invalid authentication token
content:
application/json:
schema:
type: object
properties:
message:
type: string
servers:
- url: https://mag-gpt-nextjs.vercel.app/api
/portfolios/prices:
post:
description: |
Prices for portfolios. Fetch prices on specific dates to calculate returns for custom periods
using the formula: priceOnEndDate/priceOnStartDate-1. Start date should be the last day of the previous period, not the first day of the current.
summary: Portfolio Historical Price Data
operationId: getPortfoliosPrices
requestBody:
required: false
content:
application/json:
schema:
type: object
properties:
startDate:
type: string
format: date
description: |
Start date for the period. The format is ISO 8601: yyyy-mm-dd.
If the date is not found, the API will use the closest date.
If no start date is provided, the API will return prices for the earliest date in the dataset.
endDate:
type: string
format: date
description: |
End date for the period. The format is ISO 8601: yyyy-mm-dd.
If the date is not found, the API will use the closest date.
If no end date is provided, the API will return prices for the most recent date in the dataset.
required:
- startDate
- endDate
responses:
'200':
description: Success
content:
application/json:
schema:
type: array
items:
type: object
properties:
riskLevel:
type: string
description: The risk level of the portfolio.
segment:
type: string
description: The client segment, typically either Infinity or Advisor.
historicalData:
type: array
items:
type: object
properties:
date:
type: string
format: date
description: |
The date for the historical data point.
The provided format is ISO 8601: yyyy-mm-dd.
price:
type: number
description: |
The price of the portfolio on the close of the specified date.
Use the price to calculate returns for custom periods.
required:
- date
- price
required:
- riskLevel
- segment
- historicalData
'400':
description: Bad Request - Error fetching prices
content:
application/json:
schema:
type: object
properties:
message:
type: string
'401':
description: Unauthorized - Authentication token not provided
content:
application/json:
schema:
type: object
properties:
message:
type: string
'403':
description: Forbidden - Invalid authentication token
content:
application/json:
schema:
type: object
properties:
message:
type: string
'405':
description: Method Not Allowed - The request method is not supported for this endpoint
content:
application/json:
schema:
type: object
properties:
message:
type: string
servers:
- url: https://mag-gpt-nextjs.vercel.app/api
AI Speaker & Consultant | Helping Organizations Navigate the AI Revolution | Generated $50M+ Revenue | Talks about #AI #ChatGPT #B2B #Marketing #Outbound
9 个月The impact and versatility of ChatGPT Plugins is truly groundbreaking!