I do not see how you get around this,
Don’t include irrelevant, unnecessary, or deceptive terms or instructions in the plugin manifest, OpenAPI endpoint descriptions, or plugin response messages.
Don’t include irrelevant terms or instructions in the plugin response message.
How, exactly, do you imagine serving an ad that is genuinely relevant to the chat?
And by genuinely relevant I mean in more than a tangential way.
If I’m not talking about actually wanting to buy a product how can you possibly inject an advertisement?
Using your actual example where an ad was served for the Washington Post, please share an example prompt where that would be even remotely appropriate.
Remember, you are creating a platform for plugin developers to serve ads in order to monetize.
So, presumably, they will only receive a very small amount of context from the model based on what endpoint of their API the model chooses to call.
Do you really feel comfortable trusting your ability to identify genuinely relevant ad content from whatever very small amount of information is actually sent to the plugin?
What will your policy be for plugin-developers who have their plugin pulled from the plugin store for violating the relevancy rule in the terms?
What if their entire account is shut down for violating the terms because your product injected irrelevant content into their plugin response?
I see this whole enterprise fraught with peril.
You need to remember the ad you serve becomes part of the context and is treated as factual by the model for as long as it remains in context.
The ads you serve will become part of the training data for future models.
This is not the way forward for monetization of plugins. The only ways forward I see are,
- Direct payments, either subscription or pay-per-use.
- Revenue sharing with OpenAI.